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

Re: [CSS2.1] collapsing margins min or max height

From: Alan Gresley <alan@css-class.com>
Date: Thu, 17 Mar 2011 20:08:32 +1100
Message-ID: <4D81CF90.5050902@css-class.com>
To: "L. David Baron" <dbaron@dbaron.org>
CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On 17/03/2011 3:10 AM, L. David Baron wrote:
[snip]
> I believe your observations about implementations are correct, but
> that your statement of what the spec requires is incorrect, at least
> as of the latest editor's draft:
> http://www.w3.org/Style/css2-updates/draft-PR-CSS21-201103XX/box.html#collapsing-margins
> which says the following:
>   * Nonzero min-height does NOT prevent collapsing of a block's
>     bottom margin with the bottom margin of its last child.
>   * Nonzero min-height DOES prevent collapsing of a block's own top
>     and bottom margins, UNLESS the block's top margin collapses with
>     its last child's bottom margin.  (The "UNLESS" bit comes from the
>     statement that "A collapsed margin is considered adjoining to
>     another margin if any of its component margins is adjoining to
>     that margin.")
>
> Also see the comments on (MC1) in
> http://lists.w3.org/Archives/Public/www-style/2011Mar/0346.html
>
>
> If you do not accept this resolution, please let us know by March
> 18, 2011.
>
> -David


I support this resolution. I see no benefit or use case for CSS authors 
with the current Gecko behavior.



-- 
Alan http://css-class.com/

Armies Cannot Stop An Idea Whose Time Has Come. - Victor Hugo
Received on Thursday, 17 March 2011 09:09:10 GMT

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