Closed
Bug 52112
Opened 25 years ago
Closed 25 years ago
Re-positioned DIV elements overlap badly with overflow:auto
Categories
(Core Graveyard :: GFX, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: geraint.edwards, Assigned: kmcclusk)
Details
I am not sure if this is a repeat of bug:39621 as it does not require a specifi
z-index to be set and half of it works!
This following fails in Mozilla/5.0 (X11; U; Linux 2.2.14-15mdk i686; en-US;
m18) Gecko/20000908
<HTML>
<HEAD>
</HEAD>
<BODY >
<DIV id='div1'
STYLE='position:absolute;top:100;left:100;height:160;width:165;border-width:10;border-Color:red;border-style:solid;overflow:auto;visibility:hidden'>
<IMG src='bin2.jpg' >
</DIV>
<DIV id='div2'
STYLE='position:absolute;top:150;left:150;height:160;width:165;border-width:10;border-color:yellow;border-style:solid;overflow:auto;visibility:hidden'>
<IMG src='bin2.jpg' >
</DIV>
<SCRIPT>
document.getElementById('div2').style.visibility='visible';
document.getElementById('div1').style.visibility='visible';
</SCRIPT>
</BODY>
</HTML>
Use any image that fits or exceeds the dimensions of the DIV element.
Notice how the borders and images overlap inconsistently. The border of div2 is
above everything but the image of div1 is above the image of div2!
Comment 1•25 years ago
|
||
updating component
Assignee: asa → clayton
Component: Browser-General → HTML Element
QA Contact: doronr → lorca
Comment 2•25 years ago
|
||
Triaging to compositor based on description. Cc'ing the usual suspects.
Assignee: clayton → kmcclusk
Component: HTML Element → Compositor
QA Contact: lorca → petersen
Works for me in Win32, with or without the new view manager.
Testing with the new milestone release - the problem appears to be rectified.
Tested using Mozilla/5.0 (X11; U; Linux 2.2.14-15mdk i686; en-US; m18)
Gecko/20001010
Comment 5•25 years ago
|
||
Reporter says "it works" so marking WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•