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

RE: [css3-flexbox] ED updated: algorithms and 'flex' property

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Fri, 17 Feb 2012 05:14:52 +0000
To: Tony Chang <tony@chromium.org>, Tab Atkins Jr. <jackalmage@gmail.com>
CC: "www-style@w3.org list" <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928412E5E48A@TK5EX14MBXC214.redmond.corp.microsoft.com>
± From: tc@google.com [mailto:tc@google.com] On Behalf Of Tony Chang
± Sent: Thursday, February 16, 2012 12:10 PM
± Why is the initial value of flex 'none'?  Why can't it be '0 0 auto' or 'auto'?

It certainly could be "0 0 auto". The problem I have with that is that usually when you have a set of default values and change one, the others still have defaults. 

This looks weird to me:

	"flex:initial"	== "0 0 auto"
	"flex:1"		== "1 0 0px"	
	"flex:0px"		== "1 0 0px"	
	"flex:auto"		== "1 0 auto"

It seems that a property is getting one value set, but it is also applying different defaults.

When default is "none" or any other special keyword rather than a string of multiple defaults, it is clear (I hope) that it is applied by different rules.

Perhaps instead of 'none' it could be called 'noflex' ?

BTW these special values wouldn't be problematic if 'flex' property behaved like most others - omitted values that are same as default. Then the default would be "0 0 auto" ant to change any default you have to set it. That would be my preference too.

± I find the use of 'auto' for preferred size meaning the value of width or 
± height confusing.  Can we name it something else?

Maybe. Have better ideas? 'box'?
Received on Friday, 17 February 2012 05:15:26 UTC

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