Closed Bug 294227 Opened 20 years ago Closed 20 years ago

Bad rendering of div boxes positioned by CSS that contain images on initial page load

Categories

(Core :: Layout, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: p_kilgo, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

In http://oep.yi.org/~pkilgo/misc/spain/, the header box is rendered small at
first page load (the images in it haven't loaded), and as soon as the images
load, the box is stretched under the grey box. On a refresh, it is rendered
correctly with the head box above the grey box (because images are cached?).

Reproducible: Always

Steps to Reproduce:
1. Visit a page with a non-absolute <div> with images in it and an absolute
<div> under it.
2. Refresh the page.
3. Ctrl + shift + R the page.

Actual Results:  
1. The non-absolute (header) <div> loaded stretched under the <div> below it.
2. The page loaded correctly with none of the <div>'s overlapping.
3. The page returned to it's initial state with the lower <div> overlapping the
upper <div>.

Expected Results:  
The page should have loaded correctly with none of the <div>'s overlapping on
all steps.

I thought this might have been related to tweaking http pipelining to load pages
faster, but my firefox did not have the tweak.

Pages can be written around this, but I think my expected results are how it's
supposed to be loaded since it renders correctly when loading from cached
information, and IE renders it with the expected results.
I see the described problem in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.7.8) Gecko/20050509 Firefox/1.0.4

I do not see the problem in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.8b2) Gecko/20050514 Firefox/1.0+ ID:2005051410

I'm going to mark this RESOLVED WORKSFORME as many rendering issues with firefox
1.04 have been fixed on the trunk, and this looks like another one of them.

Paul, if you want to test this yourself then try a firefox trunk (1.1alpha)
build from
http://ftp.uni-erlangen.de/pub/mozilla.org/firefox/nightly/latest-trunk/
I'd recommend you use a new profile if you are going to try this alpha build.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Tested in nightly from above site: 
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050516 Firefox/1.0+
WFM. Bug seems fixed on trunk.
You need to log in before you can comment on or make changes to this bug.