W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: [css3-flexbox] Best way to denote flexible lengths

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 13 Apr 2011 17:16:16 -0700
Message-ID: <BANLkTi=FnyO+sAxv++EWa732jBOjxdHmcg@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: www-style list <www-style@w3.org>
On Wed, Apr 13, 2011 at 5:09 PM, Alex Mogilevsky <alexmog@microsoft.com> wrote:
> With some other properties we have space separated lists where arguments can go in an order. Is there a precedent in applying that to functional notation? Then flex(auto,2) could mean same as flex(2,auto). And flex(1)==flex(auto). It would seem consistent with other syntax where people don't have to remember argument order when arguments are strongly typed.

If we did do this, I'd probably want to omit the commas entirely, and
just make it a function that takes space-separated arguments in any
order.  Radial gradients do this a little bit - the <position> is
fairly loose in its ordering (inherited from background-position), and
the size/shape argument can accept the two keywords in either order.

Alternately, scrap the flex() function entirely, and change the
width/height properties to accept a <length> and up to two
<fraction>s, so you can just write "width: 2fr" for some absolute
flex, or "width: auto 1fr 1fr" for some relative flex that can both
grow and shrink.  Is this acceptable for Grid?

Received on Thursday, 14 April 2011 00:17:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:45 UTC