- From: <bugzilla@jessica.w3.org>
- Date: Sun, 04 Mar 2012 10:55:11 +0000
- To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16226 Summary: Margin collapsing: Clarify Note in 8.3.1 to use computed values of properties Product: CSS Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: CSS Level 2 AssignedTo: bert@w3.org ReportedBy: antonsforums@yahoo.co.uk QAContact: public-css-bugzilla@w3.org Reported by Anton Prowse 8.3.1 says, in the long Note: # - The bottom margin of an in-flow block box with a 'height' # of 'auto' and a 'min-height' of zero collapses with its # last in-flow block-level child's bottom margin if the box # has no bottom padding and no bottom border and the child's # bottom margin does not collapse with a top margin that has # clearance. # - A box's own margins collapse if the 'min-height' property # is zero, and it has neither top or bottom borders nor top # or bottom padding, and it has a 'height' of either 0 or # 'auto', and it does not contain a line box, and all of its # in-flow children's margins (if any) collapse. The values in question of the 'height' and 'min-height' properties are *computed* values, but this is not clear in the prose. Now, the spec often fails to be explicit about values being computed values, and this part of 8.3.1 is just a Note, and the normative prose in 8.3.1 (of which the Note is just a summary of consequences) is explicit in its use of computed values. So this bug does not have especially high importance. However, the distinction of whether it's the used value or the computed value of 'height' used in 8.3.1 is important to the application of 'min-height' and 'max-height' in 10.7, and so clarifying the Note above would remove a potential, albeit small, source of confusion. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 4 March 2012 10:55:13 UTC