Open
Bug 616334
Opened 14 years ago
Updated 2 years ago
implement float rules 3 and 7 correctly for floats not intersecting containing block
Categories
(Core :: Layout: Floats, defect)
Core
Layout: Floats
Tracking
()
NEW
People
(Reporter: dbaron, Unassigned)
References
(Blocks 1 open bug)
Details
We currently fail four reftests in layout/floats/ that Microsoft says they've fixed and haven't gotten compatibility problems as a result of fixing.
So after Firefox 4 we should try fixing them.
They're layout/reftests/floats/...:
other-float-outside-rule-3-left-2.html
other-float-outside-rule-3-right-2.html
other-float-outside-rule-7-left.html
other-float-outside-rule-7-right.html
and in the CSS 2.1 test suite they are:
http://test.csswg.org/suites/css2.1/20101027/html4/floats-rule3-outside-left-002.htm
http://test.csswg.org/suites/css2.1/20101027/xhtml1/floats-rule3-outside-left-002.xht
http://test.csswg.org/suites/css2.1/20101027/html4/floats-rule3-outside-right-002.htm
http://test.csswg.org/suites/css2.1/20101027/xhtml1/floats-rule3-outside-right-002.xht
http://test.csswg.org/suites/css2.1/20101027/html4/floats-rule7-outside-left-001.htm
http://test.csswg.org/suites/css2.1/20101027/xhtml1/floats-rule7-outside-left-001.xht
http://test.csswg.org/suites/css2.1/20101027/html4/floats-rule7-outside-right-001.htm
http://test.csswg.org/suites/css2.1/20101027/xhtml1/floats-rule7-outside-right-001.xht
This is related to the issue previously reported as:
http://lists.w3.org/Archives/Public/www-style/2009Jan/0445.html
http://wiki.csswg.org/spec/css2.1#issue-101
Reporter | ||
Comment 1•11 years ago
|
||
It looks to me like IE fixed rule 3 but not rule 7... though the IE I'm testing isn't the latest.
Reporter | ||
Comment 2•11 years ago
|
||
Also, the tests in http://dbaron.org/css/test/2009/float-outside-tests/ are easier to check visually.
Reporter | ||
Comment 3•11 years ago
|
||
(And IE fixed rule 5. And they fixed the BFC displacement for one side but not the other!)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•