- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 17 May 2012 17:33:54 -0700
- To: Phil Cupp <pcupp@microsoft.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Thu, May 17, 2012 at 5:27 PM, Phil Cupp <pcupp@microsoft.com> wrote: > On 05/16/2012 05:55 PM, Tab Atkins Jr. wrote: >> Issue link: >> http://wiki.csswg.org/topics/css3-flexbox-rename-flex-order >> >> Should we rename the 'flex-order' property? Its functionality may be >> useful in other new layout specs, such as in Grid's auto-layout >> algorithm (which is basically a simple version of Flexbox), so putting >> it under a “flex-” prefix wouldn't be good. As well, 'flex-order' >> might be a good name in the future for putting elements in “flex >> groups”, such that one group gets first crack at the free space ahead >> of other (in the old flexbox spec, this was called 'box-flex-group'). >> >> (There are no plans right now to make this applicable to existing >> layout modes like block or table. It would simply have no effect in >> those.) >> >> A. (current spec) Name it 'flex-order'. >> >> B. Name it 'box-order'. >> >> C. Name it 'display-order'. >> >> I prefer C. > > Couple of questions to better understand the scope of the new generic order property. > > Does the re-ordering come before or after markup fix-up? If I have: > > <div style="display:flex"> > <span style="display-order:3">A</span> > <span style="display-order:1">B</span> > <div style="display-order:2">C</div> > </div> > > What do I get? > > If the A and B spans and C div above were all replaced with input tags, in what order should we tab through them? The property only works on flex items, so by definition it has to wait until after you've figured out what the flex items are. ^_^ (This is specified explicitly in the layout algorithm, though, just to avoid confusion. 'flex-order' is step 1, but figuring out flex items is step 0.) ~TJ
Received on Friday, 18 May 2012 00:34:45 UTC