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
On 1/20/15, 1:13 PM, "Florian Rivoal" <florian@rivoal.net > wrote:
>
>== 1 - Generalize 'region-fragment' ==
>
>'region-fragment'
>() apply
>to any
>fragmentainer. There is no reason to restrict it to any particular kind.
Is there a reason to restrict it to fragmentainers? Why not all block
elements?
>
>
>== 3 - Adding the ellipsis ==
>This is the least definitive part of this mail.
>
>One possible approach would be to do something similar to text-overflow.
>With
>the following syntax:
> fragmentation: auto | break [ ellipsis <string> ]?
>
>After layout, remove enough characters and atomic inlines, pushing them
>further in the fragmentation context if any
If you only allow ellipses with break, and break makes the element a
fragment container, then there is always a fragmentation context (though
possibly with just one fragment container).
>An alternative would be to do something similar to what the regions spec
>proposes as a processing model for ::after. Having 'fragmentation: break
>block-ellipsis' on a element which is overflowing (and therefore causing
>fragmentation) would insert a ::block-ellipsis pseudo element formatted
>as a
>block container, whose height reduces the available height in the
>fragmentainer. This is similar to what Tab proposed here:
> Received on Tuesday, 20 January 2015 17:43:45 UTC