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

Re: [css3-flexbox] what's the computed value of "width: flex(...)" in a non-flexbox context?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 9 Jun 2011 14:06:49 -0700
Message-ID: <BANLkTi=TmnrNWxZq4Ryaji1zUjNB8ugoWGi48BW0s6jZXhEWpg@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: Daniel Holbert <dholbert@mozilla.com>, "www-style@w3.org" <www-style@w3.org>
On Thu, Jun 9, 2011 at 12:16 PM, Alex Mogilevsky <alexmog@microsoft.com> wrote:
> ± From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf
> ± Of Tab Atkins Jr.
> ± Sent: Thursday, June 09, 2011 11:17 AM
> ±
> ± I'm inclined to have both flex() and the 'fr' unit compute to 'auto'
> ± in non-flex contexts.  We don't really need to do anything smart, because
> ± it's simply an error to use these units outside of flex-aware contexts.
>
> By "auto" you mean "initial", whatever it is for the property?
>
> I think it should be either invalid or initial. Initial probably better...

Sure, yeah.  The initial value for width/height is 'auto', and flex
units aren't allowed in any other property, so it's equivalent.  Using
flex units somewhere else is the same as using an invalid value, like
setting "padding:blue;" - it just makes the declaration invalid.

~TJ
Received on Thursday, 9 June 2011 21:07:44 GMT

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