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

Re: [css3-flexbox] Computed value and flex-align/flex-item-align.

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 27 Jan 2012 11:25:37 +0100
Message-ID: <4F227BA1.50201@mit.edu>
To: www-style@w3.org
On 1/27/12 3:52 AM, Alex Mogilevsky wrote:
> ± From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
> ± Sent: Thursday, January 26, 2012 5:27 PM
> ±
> ± Computed values are evaluated as far as possible based solely on the value
> ± of other properties in the document, without relying on layout
> ± information.  'flex-item-align:auto' can be resolved based solely on the
> ± value of 'flex-align' on the parent, so it should be resolved at computed-
> ± value time.
> It sounds like I will have to add special code just to make getComputedStyle() happy.

It's not just getComputedStyle.  The computed value is also observable 
via use of "inherit" on children.  And this aspect is more important, imo.

So the real question should be:  What should happen if a child inherits 
from an element with specified "flex-item-align: auto"?  Should it 
inherit "auto", or should it inherit something else?

Note that there may be good reasons to inherit as "auto", in which case 
the computed value should be "auto".  There's nothing that says computed 
values have to be as resolved as you can get; what they _should_ be is 
whatever makes the most sense to inherit.

Received on Friday, 27 January 2012 10:26:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:10 UTC