W3C home > Mailing lists > Public > www-style@w3.org > May 2012

Re: [css3-flexbox] min-width/height: auto, its Computed Value line, and "computes to" prose

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 19 May 2012 15:44:32 -0700
Message-ID: <CAAWBYDCxah0gax2Wn3KqSXyxnJQvRTGWWsv9J9yLp5zTD+GgUw@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: www-style@w3.org
On Sat, May 19, 2012 at 11:45 AM, L. David Baron <dbaron@dbaron.org> wrote:
> http://dev.w3.org/csswg/css3-flexbox/#min-size-auto says:
>  #  New Computed Value:   the percentage as specified or the
>  #                        absolute length or a keyword
> where the "or a keyword" is an addition relative to
> http://www.w3.org/TR/CSS21/visudet.html#min-max-widths .
>
> However, it also says:
>  # On any other element, this keyword computes to ‘0’ (unless
>  # otherwise defined by a future specification).
> The use of "computes to" here seems to contradict the "Computed
> Value" line.

They're not intended to contradict, it's just sloppy writing on our part.

> I think the "New Computed Value" line is correct, the 'auto' keyword
> should always be the computed value, and the second quoted piece of
> prose should be changed to avoid the term "computes".
>
> This would avoid implementation complexity and the need to update
> http://wiki.csswg.org/spec/property-dependencies to reflect this
> additional dependency.

What effect would this have on Block Layout margin-collapsing, which
assigns special meaning to a min-height other than 0?

~TJ
Received on Saturday, 19 May 2012 22:45:23 GMT

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