{inc} {css1} clear not working on inital load, causing weird overlap of floats

VERIFIED FIXED in M11

Status

()

Core
Layout
P3
normal
VERIFIED FIXED
19 years ago
19 years ago

People

(Reporter: David Baron, Assigned: buster)

Tracking

({css1})

Trunk
Other
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
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.

Updated

19 years ago
Severity: normal → minor
Status: NEW → ASSIGNED
Priority: P3 → P4
Target Milestone: M6
(Reporter)

Comment 1

19 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.
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
Still occurs with the 19990614 build.
(Reporter)

Comment 3

19 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.
(Reporter)

Comment 4

19 years ago
See bug 7400 for that problem with the boxacidtest.

Updated

19 years ago
Severity: minor → normal
Priority: P4 → P3
Target Milestone: M15 → M11

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 5

19 years ago
Fix just landed.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 6

19 years ago
With the Sept 23rd build, this problem appears to be fixed.
Keywords: css1
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.