Closed
Bug 134645
Opened 23 years ago
Closed 21 years ago
Floats taken into account calculating the height of a float
Categories
(Core :: Layout: Floats, defect, P2)
Core
Layout: Floats
Tracking
()
RESOLVED
INVALID
Future
People
(Reporter: emeyer, Assigned: dbaron)
References
Details
(Keywords: css1, testcase, Whiteboard: [CSS WG])
Attachments
(1 file)
2.55 KB,
text/html
|
Details |
Tests show that Mozilla is considering floated elements when calculating the
height of floated non-replaced elements, in contradiction to CSS2:10.6.3
(http://www.w3.org/TR/REC-CSS2/visudet.html#q17), which states that only
children in the normal flow are taken into account when calculating the height
of floated non-replaced elements. This was apparently not a problem in the
0.9.4 era. Testcase to follow.
Reporter | ||
Comment 1•23 years ago
|
||
This testcase, derived from a case created by Brian Costner, shows that a
right-floated 'div' is differently drawn than a normal-flow 'div' where both
have exactly the came content. CSS2:10.6.3 says they should look the same.
Reporter | ||
Updated•23 years ago
|
Attachment #77041 -
Attachment description: Flaoted div and normal-flow div showing different behaviors → Floated div and normal-flow div showing different behaviors
Assignee | ||
Comment 2•23 years ago
|
||
This is a case that I think the working group has discussed, but I'm not sure if
there was a decision. I think that the definition of 'auto' height on floats
should make it include other floats within its "formatting context". I may have
discussed this a bit at the Redmond City F2F.
Assignee | ||
Comment 3•23 years ago
|
||
See http://lists.w3.org/Archives/Member/w3c-css-wg/2001OctDec/0264.html (no
decision, though)
Assignee | ||
Comment 4•23 years ago
|
||
Also, the second and particularly the third of "the whiteboard notes" listed in:
http://lists.w3.org/Archives/Member/w3c-css-wg/2001OctDec/0289.html
Assignee | ||
Comment 5•23 years ago
|
||
What does WinIE do here? (And MacIE?)
Reporter | ||
Comment 6•23 years ago
|
||
IE/Mac and IE/Win do what Mozilla does now, but if it's not in the spec, hasn't
been errata'd, and the WG hasn't reached a decision, then I'm pretty sure we'd
be wrong to violate the specification. (Or has that idea changed of late?
Because if so, I have a few things I want to see change in Mozilla, like yesterday.)
Assignee | ||
Comment 7•23 years ago
|
||
It seemed like we pretty much agreed on it, although it wasn't formally decided
since it's not really appropriate for errata -- but rather, for changes in css3.
Speaking of which, did we formally agree on the "lost errata" for clip? They're
not in the errata either. The errata are hopelessly out of date, and many
things that we decide aren't formally noted as consensus and/or never get done.
Comment 8•23 years ago
|
||
I seem to recall a decision in Oslo whereby a float containing only another
float, where the outer float had auto dimensions, and the inner float had a non
zero fixed size, would result in the outer float overlapping the outer-most
in-flow text, and the outer float having zero size.
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Component: Style System → Layout
Keywords: css1
Priority: -- → P2
Whiteboard: [CSS WG]
Target Milestone: --- → Future
Comment 9•23 years ago
|
||
This is probably because of the changes for bug 52242, no?
Depends on: 52242
Assignee | ||
Updated•23 years ago
|
Component: Layout → Layout: Floats
Assignee | ||
Comment 10•21 years ago
|
||
This is clear in CSS 2.1, which should reach CR quite soon. (The version in the
public draft is clear but slightly garbled. The CR should be better.)
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•