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

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

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Fri, 27 Jan 2012 00:31:31 +0000
To: Daniel Holbert <dholbert@mozilla.com>, Tab Atkins Jr. <jackalmage@gmail.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928412E1DC0D@TK5EX14MBXC218.redmond.corp.microsoft.com>
± From: Daniel Holbert [mailto:dholbert@mozilla.com]
± Sent: Thursday, January 26, 2012 11:59 AM
± What should "auto" compute to for elements that *aren't* inside of a
± flexbox? (in which case there is no flexbox to derive the "flexbox's
± ‘flex-align’" from)

It seems it is again an issue with trying to arrive to final effective value at style cascading as opposed to interpreting the values in layout. 

Sorry if I don't fully understand the meaning of the word "computes", but in my understanding "flex-item-align:auto" has to behave as follows

	1) When applied to any element, the value is stored as 'auto'
	2) When queried from the element (flexbox item or not), the value is returned as 'auto'
	3) Flexbox layout, at cross-axis alignment stage
		a) retrieves 'flex-item-align' property from each flexbox item
		b) if it is not 'auto', that is the item's alignment
		c) if it is 'auto', alignment type set in flexbox's 'flex-align' property is used.

Or are there any other expectations? Or something else I don't get?
Received on Friday, 27 January 2012 00:32:14 UTC

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