Closed
Bug 1345
Opened 26 years ago
Closed 26 years ago
{vmargin} margins and floaters interaction
Categories
(Core :: Layout, defect, P2)
Tracking
()
VERIFIED
FIXED
M6
People
(Reporter: kipp, Assigned: buster)
References
Details
because top margin application is deferred until *after* a block frame is
reflowed, it's possible that the application of the margin will cause the
band-data to change (because the Y coordinate may end up moving past an impacted
region in the spacemanager). The implication is that a second reflow will need
to be done (sigh).
Alternatively, we can add a seperate "compute carried out margins" pass...
here is some sample html that demonstrates the problem.
<HTML>
<HEAD>
<STYLE type="text/css">
</STYLE>
</HEAD>
<BODY>
<IMG SRC="woofer.gif" align=left>
<H2 style="margin: 0px;">This is a run-in heading </H2>
<P style="margin: 0px;">Or is it? Enquiring minds <B>want</B> to know!
<H2>This is NOT a run-in heading </H2>
<B>Because this is an inline frame following the run-in frame</B>
</BODY>
</HTML>
|
||
Comment 4•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
See also test2 in the viewer and bug #1348 for other examples.
Summary: margins and floaters interaction → {vmargin} margins and floaters interaction
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed. test2 in viewer now flows around the floater properly.
|
||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
|
|
||
Comment 8•26 years ago
|
||
Fixed in April 5th Build.
You need to log in
before you can comment on or make changes to this bug.
Description
•