Closed
Bug 4572
Opened 26 years ago
Closed 25 years ago
{inc} {css1} clear not working on inital load, causing weird overlap of floats
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: dbaron, Assigned: buster)
References
()
Details
(Keywords: css1)
On initial load, the clear below the test that begins (roughly) "See the
description on the right hand side." doesn't work, causing the large float
there to overlap with the HR just below and the floats in the next two tests.
Even if it was just the clear not working, the floats wouldn't overlap. It's
as if everything is moved up, under the bad float. It all goes away on reflow.
Severity: normal → minor
Status: NEW → ASSIGNED
Priority: P3 → P4
Target Milestone: M6
Reporter | ||
Comment 1•26 years ago
|
||
I think I'm seeing a similar problem on
http://style.verso.com/boxacidtest/half/
and it seems that the problem may have something to do with the container of
the float being collapsed away.
Updated•26 years ago
|
Summary: {inc} clear not working on inital load, causing weird overlap of floats → {inc} {css1} clear not working on inital load, causing weird overlap of floats
Comment 2•26 years ago
|
||
Still occurs with the 19990614 build.
Reporter | ||
Comment 3•26 years ago
|
||
There are problems with the half-size boxacidtest having to do with rounding.
See bug 4098.
The boxacidtest problem is probably a separate bug, since it doesn't strictly
have anything to do with clear. It has more to do with the BODY element, since
it occurs in http://style.verso.com/boxacidtest/vd/ on initial load but not in
http://style.verso.com/boxacidtest/divs/ . What happens there is that the text
is not flowed around the floats.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•25 years ago
|
||
With the Sept 23rd build, this problem appears to be fixed.
Comment 7•25 years ago
|
||
Migrating from {css1} to css1 keyword. The {css1}, {css2}, {css3} and {css-moz}
radars should now be considered deprecated in favour of keywords.
I am *really* sorry about the spam...
You need to log in
before you can comment on or make changes to this bug.
Description
•