Closed Bug 1378 Opened 26 years ago Closed 26 years ago

{vmargin} collapsing margin problems

Categories

(Core :: Layout, defect, P2)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: buster)

References

()

Details

The top and bottom margins of the ULs in the above page seem to disappear, but they are actually there (I think), but just not colored with the background color of the DIV that surrounds them.
Status: NEW → ASSIGNED
I just realized this is a collapsing margins problem, but I still think your current choice of colors in the collapsing margin is not optimal, especially in the middle one where both sides are the same color (there is a </DIV><DIV> between the margins, but that shouldn't make a difference).
Summary: margin problems → collapsing margin problems
At the URL http://www.w3.org/Style/CSS/Test/current/sec411.htm , nested margins do not collapse. However, you are collapsing them in the URL above. They should be collapsed, per the spec, but I don't like it, because of what happens in the URL above (http://www.fas.harvard.edu/~dbaron/csstest/listbox.html).
Setting all current Open/Normal to M4.
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
QA Contact: 4144 → 4110
Summary: collapsing margin problems → {vmargin} collapsing margin problems
Severity: normal → major
Actually, based on the errata for section 10.6.3, you are currently handling this correctly: http://www.w3.org/Style/css2-updates/REC-CSS2-19980512-errata.html That part of the bug is invalid. However, the problems with classes five/six/seven of http://www.w3.org/Style/CSS/Test/current/sec411.htm remain.
The test lays out correctly. note that the bullets for the first div section's 3rd div (the "condensed" one) will be invisible because they are off the screen to the left...
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Verified fixed.
You need to log in before you can comment on or make changes to this bug.