Closed Bug 4831 Opened 25 years ago Closed 23 years ago

[FLOAT] float should not be higher than earlier float on opposite side

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: waterson)

References

(Blocks 1 open bug, )

Details

(Keywords: css1, helpwanted, testcase, Whiteboard: [Hixie-P3] important floater bug | relnote-devel)

Floats should not be higher than an earlier float on the opposite side.  See
the second test in the above URL.

IE5 does get this correct.
Assignee: troy → kipp
Status: NEW → ASSIGNED
Summary: float should not be higher than earlier float on opposite side → {css1} float should not be higher than earlier float on opposite side
QA Contact: 4144 → 4110
This looks like it's been fixed sometime since April...
Never mind.  It's not fixed.  I was misreading the test...
Updating to default Layout Assignee...kipp no longer with us :-(
Why are you re-reassing layout bugs? Do NOT touch layout bugs.

The bugs are assigned to Kipp so they can stay neatly organized until we have a
new owner for the block/inline code.
Summary: {css1} float should not be higher than earlier float on opposite side → {css1} [FLOAT] float should not be higher than earlier float on opposite side
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...
Summary: {css1} [FLOAT] float should not be higher than earlier float on opposite side → [FLOAT] float should not be higher than earlier float on opposite side
mine! mine mine mine!  all mine!  whoo-hoo!
Assignee: kipp → buster
Nom. nsbeta3, recc. nsbeta3+. css1 compliance that IE5 gets right; when IE5 is 
getting part of CSS right, we don't want a Gecko bug to prevent it from being 
usable by the web.
Keywords: nsbeta3
Keywords: relnote2
QA Contact: chrisd → py8ieh=bugzilla
Whiteboard: hit during nsbeta2 standards compliance testing
Denying for beta3: bigger problems to solve in very limited time - sorry.
Whiteboard: hit during nsbeta2 standards compliance testing → hit during nsbeta2 standards compliance testing [nsbeta3-]
Target Milestone: M17 → Future
We still fail this, which EVEN INTERNET EXPLORER 5 GETS CORRECT. By not 
fixing this we are making the 'float' property unreliable for web authors, 
since we would be displaying it incorrectly while the competition would be 
doing it right.
Severity: normal → major
Hardware: Other → All
Whiteboard: hit during nsbeta2 standards compliance testing [nsbeta3-] → [nsbeta3-] hit during nsbeta2 standards compliance testing
I know we still do not have enough resources to get this fixed. However:

Removing [nsbeta3-] to put this floater bug (and 3 others) back onto the 
developer radar, as per suggestion by Gerardo.
Keywords: helpwanted
Whiteboard: [nsbeta3-] hit during nsbeta2 standards compliance testing → (beta3 minus per triaging) hit during nsbeta2 standards compliance testing
changed (beta3 minus per triaging) to [nsbeta3-] so searches work correctly
Status: NEW → ASSIGNED
Whiteboard: (beta3 minus per triaging) hit during nsbeta2 standards compliance testing → [nsbeat3-] hit during nsbeta2 standards compliance testing
Whiteboard: [nsbeat3-] hit during nsbeta2 standards compliance testing → [nsbeta3-] hit during nsbeta2 standards compliance testing
Keywords: relnote2
Summary: [FLOAT] float should not be higher than earlier float on opposite side → [FLOAT] float should not be higher than earlier flat on opposite side
Whiteboard: [nsbeta3-] hit during nsbeta2 standards compliance testing → [nsbeta3-] relnote-devel hit during nsbeta2 standards compliance testing
Summary: [FLOAT] float should not be higher than earlier flat on opposite side → [FLOAT] float should not be higher than earlier float on opposite side
Keywords: nsbeta3nsbeta1
Whiteboard: [nsbeta3-] relnote-devel hit during nsbeta2 standards compliance testing → relnote-devel
Whiteboard: relnote-devel → [Hixie-P3] important floater bug | relnote-devel
Blocks: float
Taking, as I have a fix for this in bug 59200.
Assignee: buster → waterson
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Depends on: 59200
Target Milestone: Future → ---
Fixed with changes in bug 59200.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
VERIFIED!!!!!!!!!!!!!!!!!!!!!!! Waterson rules!!!!!!!!!!!!!!!!! 
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.