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

Re: [css-containment][css-regions] how does containement and regions interact

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 1 Jul 2015 15:30:01 -0700
Message-ID: <CAAWBYDA7Hq0CWhs9Lpt0mWdu1txxANx6t5kSW62tt3SsWFf9UA@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: www-style list <www-style@w3.org>
On Wed, Jul 1, 2015 at 2:34 PM, Florian Rivoal <florian@rivoal.net> wrote:
> This is tricky to phrase well. Which of these 2 (meant to be equivalent) do you like best?
> The first <a>CSS Region</a> in a region chain which is either:
>   - an element with <a>layout containment</a> itself or
>   - the last of one or more regions in this chain
>     to be descendants of the same element with <a>layout containment</a>
> is treated as if it was the last region in the chain, and gets all the
> remaining content in the associated <a>named flow</a>. Subsequent regions
> in the chain do not receive any content from the <a>named flow</a>.

Slightly prefer this one.

> In either case, we should probably also says what happens in the CSSOM.
> I suggest that:
>   - these subsequent regions that don't get content are
>     still considered part of the region chain as returned from the
>     getRegions() method of the NamedFlow interface (if you don't want
>     that, use contain:style)
>   - the regionOverset attribute of the Region interface of the region
>     which eats all the content is set to overset if the content doesn't
>     fit. The current regions spec only allows this value on the last
>     region in the chain, but it's behaving as if it was.

Yes to both.

Received on Wednesday, 1 July 2015 22:30:48 UTC

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