Closed
Bug 347784
Opened 19 years ago
Closed 17 years ago
absolute div under div with overflow value assigned not rendered well
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: hagayg, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
|
824 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
in the following html you can see only the "yellow" div and not the "maroon" div
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Untitled Page</title>
</head>
<body style="height:100%;padding:0px;margin:0px;">
<div style="background-color:red;position:absolute;left:0px;top:0px;width:100%;height:100%;z-index:100;">
</div>
<div style="overflow:auto;width:100%;background-color:Gray;">
<div style="position:absolute;left:200px;top:200px;background-color:Maroon;z-index:200;height:100px;width:100px;"></div>
</div>
<div style="width:100%;background-color:Gray;">
<div style="position:absolute;left:400px;top:200px;background-color:yellow;z-index:200;height:100px;width:100px;"></div>
</div>
</body>
</html>
Reproducible: Always
Steps to Reproduce:
1.just check the html
Updated•19 years ago
|
Component: General → Layout
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → 1.8 Branch
Comment 1•19 years ago
|
||
This is worksforme with current trunk build.
Comment 2•19 years ago
|
||
Please try and see if it works for you with current trunk build:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
(In reply to comment #2)
> Please try and see if it works for you with current trunk build:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
dont know what trunk is, also tested with firefox 2.0 beta 1 , doesnt work well there either...
Comment 4•19 years ago
|
||
Well, you can download trunk builds with the link I gave to you.
I know it doesn't work well in Firefox2.0 beta 1.
Maybe you're not comfortable downloading a trunk build? That's no problem.
(In reply to comment #4)
> Well, you can download trunk builds with the link I gave to you.
> I know it doesn't work well in Firefox2.0 beta 1.
> Maybe you're not comfortable downloading a trunk build? That's no problem.
as i said i dont know what trunk is, I only know that it doesnt work in firefox at the moment, whether it work in trunk, dosent matter me much since my customers uses only firefox & internet explorer (which this bug doesnt happen there) , at the moment i made workaround in my software not to render "overflow" in the style for this case (luckly i dont need it in this case) but it just took me 6 hours to find this bug out, hopefully it will save many others this kind of effort... if this bug get fixed (and it will make my software bit more elegant by removing this exception :) )
Comment 6•19 years ago
|
||
Yes, I know it doesn't matter for you much, but bugzilla is for internal bug tracking, so I like to mark this bug worksforme, because this is something that is already fixed on trunk somehow.
Can I do that, or don't you agree?
(In reply to comment #6)
> Yes, I know it doesn't matter for you much, but bugzilla is for internal bug
> tracking, so I like to mark this bug worksforme, because this is something that
> is already fixed on trunk somehow.
> Can I do that, or don't you agree?
Sorry , I am kinda new here (actually this is my second bug report) , i dont know what worksforme means, i dont know what trunk is (is it firefox 3 "engine" or something like that ?) so i cant answer your question.
What i do know is when this bug wont happen in future firefox versions (hopefully 1.5.7 :) ) this bug will be closed from my point of view
Comment 8•19 years ago
|
||
Yeah, current trunk builds are what Firefox 3 eventuall will come out with.
The release of Firefox 3 will be somewhere next year, so you won't get to see a version that has the fix very soon, I'm afraid (unless you're trying a trunk build).
(In reply to comment #8)
> Yeah, current trunk builds are what Firefox 3 eventuall will come out with.
> The release of Firefox 3 will be somewhere next year, so you won't get to see a
> version that has the fix very soon, I'm afraid (unless you're trying a trunk
> build).
O.K , I understand this bug wont get fixed soon.
Or i am not sure , but you are saying that if i'll confirm this bug is fixed in the latest trunk builds it might get fixed in firefox 1.5/2 releases ? or i misunderstood what you meant ?
Comment 10•19 years ago
|
||
No, it doesn't matter that much if you confirm this bug is fixed or not in the latest trunk builds.
It only matters to this bug. If you confirm this bug is fixed in the trunk builds, then I can mark this bug worksforme.
Comment 11•17 years ago
|
||
I think this can now be closed as WFM.
While the bug is in Fx2 it is not in Fx3 and trunk. Most likely due the reflow refactoring.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•