W3C home > Mailing lists > Public > www-style@w3.org > March 2011

RE: [CSS21] 10.6.1, 10.6.3 and 10.6.7 - editorial issues

From: Arron Eicholz <Arron.Eicholz@microsoft.com>
Date: Mon, 14 Mar 2011 23:57:07 +0000
To: Anton Prowse <prowse@moonhenge.net>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <07349ECFC3608F48BC3B10459913E70B12CFD60C@TK5EX14MBXC132.redmond.corp.microsoft.com>
On Monday, August 09, 2010 4:06 AM Anton Prowse wrote:
> Issue 4:
> 
> 10.6.3 (Block-level non-replaced elements in normal flow when 'overflow'
> computes to 'visible') says:
> 
>    # If it has block-level children, the height is the distance between
>    # the top border-edge of the topmost block-level child box that does
>    # not have margins collapsed through it and the bottom border-edge of
>    # the bottommost block-level child box that does not have margins
>    # collapsed through it. However, if the element has a non-zero top
>    # padding and/or top border, or is the root element, then the content
>    # starts at the top margin edge of the topmost child. (The first case
>    # expresses the fact that the top and bottom margins of the element
>    # collapse with those of the topmost and bottommost children, while in
>    # the second case the presence of the padding/border prevents the top
>    # margins from collapsing.) Similarly, if the bottom margin of the
>    # block does not collapse with the bottom margin of its last in-flow
>    # child, then the content ends at the bottom margin edge of the
>    # bottommost child.
> 
> The second sentence explains how to calculate content area height when top
> margin collapsing between parent and child is prevented by certain means.
> The second clause of the third (parenthetical) sentence explains the same
> thing, but with reference to even more restricted means.  The fourth
> sentence invokes "similarly" but goes on to explain how to calculate content
> area height when bottom margin collapsing between parent and child is
> prevented by /all/ means.
> 
> This paragraph needs editing so that it treats the top margin collapsing case in
> the same way as the bottom margin collapsing case, namely by simply
> referring to the general situation in which parent–child top margin collapsing
> is prevented.
> 
> Without this edit the spec is wrong – specifically, in the second sentence –
> since the parent element in question might have a first child with overflow
> other than visible (for example) and a positive top margin height.

Thank you for your feedback. The CSSWG resolved not to make these changes to the CSS 2.1 specification[1]. We determined that the current text is correct and there is no change needed at this time.

Please respond before 18 March, 2011 if you do not accept the current resolution.

[1] http://w3.org/TR/CSS

Received on Monday, 14 March 2011 23:57:42 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:38 GMT