- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 11 Mar 2011 13:07:33 -0800
- To: Simon Fraser <simon.fraser@apple.com>
- Cc: Arno Gourdol <agourdol@adobe.com>, Alex Mogilevsky <alexmog@microsoft.com>, w3c-css-wg <w3c-css-wg@w3.org>, "www-style@w3.org" <www-style@w3.org>
On Fri, Mar 11, 2011 at 1:04 PM, Simon Fraser <simon.fraser@apple.com> wrote: > On Mar 11, 2011, at 11:12 AM, Tab Atkins Jr. wrote: >> On Fri, Mar 11, 2011 at 11:00 AM, Arno Gourdol <agourdol@adobe.com> wrote: >>> Your proposal seems reasonable. >>> Where would Flexbox fit? It's conceivable that Flexbox could be used to do >>> some layout that you would apply story threading to. >> >> We can definitely combine threading with Flexbox, possibly through >> ::slot() to generate the region containers (and flex-index to position >> the regions in the flexbox?). > > I don't think these should be combined. We need to strive to slice and dice the modules > so that they are orthogonal to each other, so a regions spec needs to deal specifically > with flowing content between boxes, and not how those boxes are laid out. When I said "combine" I meant "use together", not "make Flexbox explicitly talk about Threading". Threading should be defined in a sufficiently generic way that it can be used with any layout model. ~TJ
Received on Friday, 11 March 2011 21:08:25 UTC