Open Bug 411657 Opened 16 years ago Updated 8 months ago

Layer move handle allways below other layers in designMode

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: haaglin, Unassigned)

References

Details

Attachments

(1 file)

Image of result
5.36 KB, image/png
Details 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20061201 Firefox/2.0.0.11 (Ubuntu-feisty)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20061201 Firefox/2.0.0.11 (Ubuntu-feisty)

In designmode, if i have a absolute positioned object in wysiwyg mode (designMode) positioned below another abspos object, the layer handle disappears below the layer on top, making it impossible to move the layer.

This bug has been there for ages, but i did not find any bug report for it. Sorry if it is already reported.

Reproducible: Always

Steps to Reproduce:
1.create an empty file (test.html)

2.paste this into the file: 
<html>
<head>
<title></title>
<meta content="">
</head>
<body>
<div style="display: block; position: relative; width: 0px; height: 0px;" id="layerContainer">
<div style="background: rgb(255, 0, 0) none repeat scroll 0%; overflow: auto; position: absolute; top: 30px; width: 200px; height: 200px;">&nbsp;</div>
<div style="background: rgb(51, 0, 204) none repeat scroll 0%; overflow: auto; position: absolute; top: 200px; width: 200px; height: 200px; left: 40px;">&nbsp;</div>
</div>

<script type="text/javascript">
document.designMode = 'on';
</script>
</body>
</html>

3.Open it, and select the blue layer and try to move it
Actual Results:  
No drag handle

Expected Results:  
Visible drag handle

I was able to fix this bug by adding this into EditorOverride.css:

span[\_moz_anonclass="mozGrabber"] {
      z-index: 2147483646 !important;
}
WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008011000 Minefield/3.0b3pre
Attached image Image of result — 
This har been tested on 20+ different computers, Linux,Windows and mac, all with the same result.
Blocks: 424615
It seems that when not using z-index, it works fine in FF3 But when using z-index, the problem occurs. Paste the following in a file, and run in firefox. Try to move the blue layer. 

<html>
<head>
<title></title>
<meta content="">
</head>
<body>
<div style="display: block; position: relative; width: 0px; height: 0px;"
id="layerContainer">
<div style="z-index: 1; background: rgb(255, 0, 0) none repeat scroll 0%; overflow: auto;
position: absolute; top: 30px; width: 200px; height: 200px;">&nbsp;</div>
<div style="z-index: 2; background: rgb(51, 0, 204) none repeat scroll 0%; overflow: auto;
position: absolute; top: 200px; width: 200px; height: 200px; left:
40px;">&nbsp;</div>
</div>

<script type="text/javascript">
document.designMode = 'on';
</script>
</body>
</html>
To fix it in FF3, i have to edit resource://gre/res/contenteditable.css, not EditorOverride as in FF2, and add 

span[\_moz_anonclass="mozGrabber"] {
      z-index: 2147483646 !important;
}
It's so easy to fix this bug, i hope it will be done soon.
Please fix this BUG! this is very urgent measure for a stable web application in firefox.
Yes - fixing it would help me as well!
I second this. Since updates overwrite contenteditable.css local editing is not a solution. I need this function for lots of customers of a web site so fixing this bug would be really appreciated.
I agree with Mr. Feldmann. Would you please fix this bug. It is absolutely essential for our web application. Thx.
Product: Firefox → Core
QA Contact: general → general
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 14 votes.
:jstutte, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jstutte)

Moving to the layout team to check if there is still an issue here.

Component: General → Layout
Flags: needinfo?(jstutte)
You need to log in before you can comment on or make changes to this bug.