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

Re: [css-flexbox] Flexbox pagination: implied break-inside:avoid

From: Florian Rivoal <florian@rivoal.net>
Date: Fri, 11 Dec 2015 12:20:43 +0900
Cc: "www-style@w3.org" <www-style@w3.org>
Message-Id: <2D2232F8-6D23-41A6-AF43-0EF616544C8B@rivoal.net>
To: fantasai <fantasai.lists@inkedblade.net>

> On 11 Dec 2015, at 08:58, fantasai <fantasai.lists@inkedblade.net> wrote:
> 
> The Flexbox spec currently says:
>  # If the first fragment of the flexbox is not at the top of the page,
>  # and some of its flexbox items don't fit in the remaining space on the
>  # page, the entire fragment is moved to the next page.
> 
> I think this needs s/some/none, i.e.
> 
>  | If the first fragment of the flexbox is not at the top of the page,
>  | and none of its flexbox items fit in the remaining space on the
>  | page, the entire fragment is moved to the next page.


After a little whiteboard session, Murakami-san and I agree with you.

While I was at it, I made a little test/demo to see how the various browsers dealt with some simple flexbox fragmentation scenarios.

http://output.jsbin.com/hezica/

Conclusions, having looked at safari/chrome/firefox/edge/presto (did not check nightlies/beta/etc):

* Firefox follows the spec that you are proposing to change, everybody else does the proposed spec

* Every single browser fragments flexbox differently, and they are all bad (some much worse than others).

-Florian
Received on Friday, 11 December 2015 03:21:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:31 UTC