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: Mon, 6 Jul 2015 14:56:05 -0700
Message-ID: <CAAWBYDA+4yz2952hHaf576B6rZdanJsYOQVn5Cg6zgZtd9REdw@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>
On Thu, Jul 2, 2015 at 7:00 AM, Alan Stearns <stearns@adobe.com> wrote:
> On 7/2/15, 3:27 AM, "Florian Rivoal" <florian@rivoal.net> wrote:
>>> On 02 Jul 2015, at 00:31, Alan Stearns <stearns@adobe.com> wrote:
>>> How about:
>>>
>>> If a fragmentation context participates in layout containment, the first
>>> element with layout containment affecting the fragmentation context must
>>> “trap” the remainder of the fragmented flow. Fragmentation must not
>>> continue past the layout containment boundary. So the last fragment
>>> container within the first layout containment boundary is treated as if
>>>it
>>> is the last fragment container in its fragmentation context.
>>
>>Not bad :) You took something awkward to phrase, generalized it to a
>>broader
>>situation, and still managed to craft a sentence that makes sense.
>>
>>I'd add:
>>
>>  If subsequent fragmentation containers in the fragmentation context
>>  are only generated when more content remains in the fragmented flow,
>>  then they are not generated. If they would exist regardless, they
>>  remain part of the fragmentation context, but do no receive any content
>>  from the fragmented flow.
>>
>>  Specifically:
>>    - CSS Regions following the one which traps the content are still
>>      considered part of the region chain as returned by the
>>      getRegions() method of the NamedFlow interface.
>>    - the regionOverset attribute of the Region interface of the region
>>      which traps the content is set to overset if the content doesn't
>>      fit, even if it is not the last region in the region chain.
>>    - If the computed value of the continue property on an element with
>>      layout containment would otherwise have been ''auto'' or
>>      ''fragments'', it must instead compute to ''overflow''.
>
> This all looks good to me. I like the general rules followed by specific
> applications of those rules.

I like this as well, and would gladly accept a PR.

~TJ
Received on Monday, 6 July 2015 21:56:52 UTC

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