W3C home > Mailing lists > Public > www-style@w3.org > December 2013

Re: [css3-flexbox][css3-align] align-* properties

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 13 Dec 2013 17:14:41 -0800
Message-ID: <CAAWBYDDfjhHkUzUuEPHxQSeEKiWt_fkTA-Rte96gti=62CY27A@mail.gmail.com>
To: "Jens O. Meiert" <jens@meiert.com>
Cc: W3C WWW Style <www-style@w3.org>
On Fri, Dec 13, 2013 at 5:06 PM, Jens O. Meiert <jens@meiert.com> wrote:
>> Yeah, this is an issue with W3C process.  It's annoying to update CR
>> drafts.  This should be fixed when we push Flexbox to PR, or when we
>> get annoyed enough at it to fix it in CR.
>
> Well, I somewhat hope reports like this help with the annoying ;)
>
>> Note that the difference isn't detectable to the page - "auto"
>> computes to "stretch" on flexboxes, so by the time you can observe the
>> value (getComputedStyle()), it's already the same value regardless of
>> which spec you're looking at.
>
> But what’s the true initial value then—or what do I miss?

The true initial value is "auto" - the Alignment spec wins.  You just
can't *see* the "auto" value on a Flexbox, since it'll turn into
"stretch" by the time you can read out the value of the property.

~TJ
Received on Saturday, 14 December 2013 01:15:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:17 UTC