- From: Glen Huang <curvedmark@gmail.com>
- Date: Tue, 20 Jan 2015 11:29:10 +0800
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style@w3.org
- Message-Id: <5466F31D-48C6-4653-BD96-B521AC3FDB4F@gmail.com>
> The one concern I have is what if this value is specified within > a flex item? I think so. This property has to work in a flex context, and the before and after position of a flex container that is not itself a flex item aren’t in such context. > We don't have a very solid definition for how flex items split yet. Just my 2 cents, but what about no other flex items can be in the same flex line before/after the flex item having a break-before/break-after property specified. Also just a quick question, is it possible to ask flex layout to ignore flex lines (or a different working mode for flex lines) and make flex items stack as tight as possible in the cross axis? The use case is to enable a jquery masonry (http://masonry.desandro.com <http://masonry.desandro.com/>) like layout. > On Jan 20, 2015, at 11:06 AM, fantasai <fantasai.lists@inkedblade.net> wrote: > > On 01/19/2015 09:52 PM, Glen Huang wrote: >> Thank you. >> >> But if I understand the fragmentation module correctly, `always` >> still introduce a page break, and `any` is a delegation like value, >> you have to define what’s the deepest fragmentation context for a >> flex layout before `any` can work in that layout. > > Yes. 'always' would still introduce a page break. 'any', if we define > flex lines as trapping it, would introduce a flex line break when > specified on a flex item. > > We could also introduce a 'flex' value, that would create a flex > line break if in a flex container, otherwise not. > > The one concern I have is what if this value is specified within > a flex item? In that case, technically, it would cause the flex > item to split across flex lines. We don't have a very solid > definition for how flex items split yet. :/ > > ~fantasai >
Received on Tuesday, 20 January 2015 03:29:44 UTC