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

Re: [css-break][css-overflow-3][css-regions][css4-ui] generalizing 'region-fragment' into a fragmentation primitive: a first step to solving multi-line ellipsis

From: Florian Rivoal <florian@rivoal.net>
Date: Wed, 21 Jan 2015 00:31:50 +0100
Cc: W3C Style <www-style@w3.org>
Message-Id: <9EFDD263-2C7C-41FC-9123-163ADDB165F0@rivoal.net>
To: Alan Stearns <stearns@adobe.com>

> On 21 Jan 2015, at 00:20, Alan Stearns <stearns@adobe.com> wrote:
>>> B. Selectors can refer to many boxes. What if the “next” selector 
>>> selects 
>>> multiple elements? What if the selector for the ‘fragmentation’ 
>>> property 
>>> selects multiple elements?
>> Pick the first one of the selected set in DOM order. If that's yourself,
>> apply the usual loop-detection safety valve and don't flow (i.e.
>> 'fragmentation'computes to 'none' or maybe 'break').
> So if my markup has multiple paragraphs, and style says:
> p { fragmentation:break insert-into(#id) }
> Only the first paragraph’s content would fragment and run through the #id 
> box? That seems bad to me.

Ah, sorry, misread you. "Pick the first in document order" was meant for the selector used in insert-into().

In the case you highlight, it would insert from every one of the p elements, in document orders. So in this case, assuming #id is empty, this would be equivalent to

p {flow-into: foo;}
#id {flow-from: foo;}

 - Florian
Received on Tuesday, 20 January 2015 23:32:14 UTC

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