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

Re: [css-page-floats] Options for floating without iterative reflow

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 16 Dec 2015 10:44:23 -0800
Message-ID: <CAAWBYDA0d6eSbnugj9qBa4qcx=3EcwNSa+shQzHc3=nRObFk=w@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: "Robert O'Callahan" <robert@ocallahan.org>, www-style list <www-style@w3.org>
On Mon, Dec 14, 2015 at 9:48 PM, Florian Rivoal <florian@rivoal.net> wrote:
>> On Dec 15, 2015, at 10:54, Robert O'Callahan <robert@ocallahan.org> wrote:
>> On Mon, Dec 14, 2015 at 8:23 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> 4. Require that floats take up the entire inline-width of the
>> fragment, or otherwise exclude lineboxes from flowing around them.
>> This means all you need to do is shift lineboxes to accommodate the
>> floats, which is cheap and not "real" layout.
>> Note that this isn't true in the presence of left/right floats.
> Presumably, these left/right floats would be pushed down together with the rest of the content,
> so that might not be a problem.

Yeah, inline floats would be pushed with the rest of the inlines.

> On the other hand, when the lines are pushed down beyond a fragmentation
> boundary, there's not guarantee that the next fragmentainer will be the same width, so you'll have to at least be able to deal with that. But it might still leave us with enough cases where it works that this could help performance.

Browsers generally only support same-width fragments right now anyway
- multicol and printing - so it's a non-issue for them.  Browsers that
do implement Regions would of course have to pick up the increasd
difficulty.  I'm happy to file this under "very cheap if the fragments
are same-size".

Received on Wednesday, 16 December 2015 18:45:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:59 UTC