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 15:08:55 -0800
Message-ID: <CAAWBYDDC-=rvA8PmWk-vtuP5_fS2wGOdcpqTYTWJoN_5n2rf+A@mail.gmail.com>
To: "Jens O. Meiert" <jens@meiert.com>
Cc: W3C WWW Style <www-style@w3.org>
On Thu, Dec 12, 2013 at 6:41 PM, Jens O. Meiert <jens@meiert.com> wrote:
> “align-content”, “align-items”, and “align-self” are specified in both
> the Flexible Box Layout Module [1-3] and the Box Alignment Module
> [4-6]. Both modules are reasonably recent (Sep 18, 2012 vs. May 14,
> 2013). Incidentally, the older draft is in the more mature CR status,
> the newer one WD. Two of the three properties’ initial values are
> different (“stretch”/“stretch” vs. “auto”/“auto”). There is a mention
> of interaction with the Flexible Box Layout Module in 1.1 of the
> Alignment draft [7], but that appears to add to the confusion rather
> than help :)
>
> There’s probably something that explains the situation? Tab, Elika,
> since you two are listed as authors of both drafts, do you see any
> low-hanging fruits to reduce confusion?

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.

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.

~TJ
Received on Friday, 13 December 2013 23:09:42 UTC

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