Closed Bug 3438 Opened 26 years ago Closed 26 years ago

{vmargin} vertical margins collapse when they shouldn't

Categories

(Core :: Layout, defect, P2)

x86
Windows NT
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: ekrock, Assigned: buster)

References

()

Details

This test fails on Seamonkey 0302 but works on IE4: There should be three centimeters between this text and the text above, but only one centimeter between this text and the text below, because vertical margins of nested elements should collapse only if there is no border or padding between the margins.
By the way, the part that fails is the "one centimeter below" part.
Assignee: peterl → kipp
Component: Style System → Layout
Status: NEW → ASSIGNED
Summary: vertical margins collapse when they shouldn't → {vmargin} vertical margins collapse when they shouldn't
Severity: normal → major
*** Bug 3961 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed. We now pass this css1 test properly; look for the fix in tommorows build.
Status: RESOLVED → VERIFIED
Paragraph 8 says 'there should be 2cm between this paragraph and the one below'. This wording is misleading to me. If 'paragraph' refers to 'text', then the page renders correctly. If 'paragraph' refers to the 'paragraph box', then the page is not rendering as per the statement. I am verifying this bug fixed based on the assumption that 'paragraph' means 'text'.
Verified bug using 4/30 Apprunner.

I consider it a critical failure to print any document with centralized margins, they should never be changed without the user's consent, since the impression should originally follow how it was generated and not the browser modify them by centering the text or content without the consent of the user. user. And I saw no option to adjust it to your preference. So much so that I am not upgrading from 87 to 88 because of this. It has already caused me severe inconvenience in issuing documents on a client of mine because of this.

You need to log in before you can comment on or make changes to this bug.