Closed Bug 1258 Opened 26 years ago Closed 26 years ago

script flushing of tags breaks layout

Categories

(Core :: Layout, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: buster, Assigned: buster)

References

()

Details

compare the page against the bitmap "correct" layout provided on this page.
Status: NEW → ASSIGNED
Steve could you explain to me about the problem. Thanx
Assignee: peterl → kipp
Status: ASSIGNED → NEW
Summary: incorrect display → incorrect display due to use of negative margins
reassigning to Kipp. The style context for each element looks correct, but they make use of negative margins.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I don't see anything wrong with the page
Status: RESOLVED → REOPENED
the page uses negative margins to overlap the ~ 1 ~ to get a drop-shadow effect. The bitmap for what the page should look like seems to be missing : ( Maybe the author could be asked for it. If you see each ~1~ duplicated, the pages isn't correct. that's what I see with today's build. Back in Nov. peter looked at this page with me and agreed it was the existence of negative margins that was the main culprit.
Status: REOPENED → ASSIGNED
Priority: P2 → P3
Summary: incorrect display due to use of negative margins → script flushing of tags breaks layout
Well I dug in furthur and here is what I found. 1. The page has now STYLE tags or LINK tags pointing to a style sheet so it's no longer a good test if it ever was. Because of this, the layout I see in nglayout, ie5 and navigator all agree and we have no problem. 2. However, the page doesn't load correctly because the process-script-tag code flushes out any pending tags before the script runs in case the script needs access to the objects previously defined. Commenting this out causes the page to load properly.
Resolution: FIXED → ---
Status: ASSIGNED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: --- → FIXED
Fixed the script flushing problem. We don't reflow until the content model is coherent.
Status: RESOLVED → VERIFIED
marking verified
You need to log in before you can comment on or make changes to this bug.