W3C home > Mailing lists > Public > www-style@w3.org > January 2015

Re: [css-flexbox] Allow specifying when wrapping should happen

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 20 Jan 2015 03:20:27 +0000
To: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <D0E3073D.23001%stearns@adobe.com>
On 1/19/15, 7:06 PM, "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. :/

All of these values (‘flex’, ‘always’ and ‘any’) would have the problem of
what to do when it’s specified within a flex item.

One possible solution would be to define break opportunities in a flex
fragmentation context to only occur between flex item boxes. So ‘flex’,
‘always’ and ‘any’ inside a flex item would not cause a flex line break.
But ‘always’ inside a flex item could create a break within some other
fragmentation context, such as when a flex container is paginated.

Thanks,

Alan

Received on Tuesday, 20 January 2015 03:20:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:56 UTC