- From: Glen Huang <curvedmark@gmail.com>
- Date: Tue, 20 Jan 2015 10:52:30 +0800
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style@w3.org
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. > On Jan 20, 2015, at 8:50 AM, fantasai <fantasai.lists@inkedblade.net> wrote: > > On 01/19/2015 02:10 AM, Glen Huang wrote: >> Thank you. Didn’t notice the `page-break-before` property. >> >> However, this doesn’t seem like a perfect solution, because it also >> introduces a page break, which means whenever I’d like to use this >> layout for definition lists, printing the web page will result in >> each page containing only one term and one description (or just one >> description, for multiple descriptions). >> >> I see the fragmentation module introduces breaks for region and >> multi-column layouts, I wonder if it makes sense to add flex layout >> to that list? Maybe something like `break-after: flex;`? > > I agree with your reasoning, and I think it would make sense for > flex layout to trap the 'always' and 'any' values of 'break-before' > and 'break-after'. > > I'll ask about bringing this up on the call this week. :) > > dholbert, any comments on that? > > ~fantasai > > p.s. I vaguely recall wanting to do something like this, actually, > but the fragmentation module wasn't ready enough at the time we were > drafting the Flexbox pagination section. >
Received on Tuesday, 20 January 2015 02:53:03 UTC