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

[css-regions][css-break] Nested & grouped regions breaking rules

From: François REMY <francois.remy.dev@outlook.com>
Date: Wed, 10 Jul 2013 23:57:08 +0200
Message-ID: <DUB120-W5397A3E4EC5F31D301794A57A0@phx.gbl>
To: "www-style@w3.org" <www-style@w3.org>
CC: "fantasai.lists@inkedblade.net" <fantasai.lists@inkedblade.net>, "Rossen.Atanassov@microsoft.com" <rossen.atanassov@microsoft.com>
TL/DR: Grouping all regions into a single breakable context is an issue if you use region clusters or a region hierarchy (nested regions). I propose thereafter a mechanism to help identify which region the breaking rules specified in the author stylesheet apply to.

Right now, you can only specify your desired breaking behavior relative to the kind of breakable content {page, column, region}. 

While that may cover a lot of use-cases, I came across a case where you may want to avoid breaking an element across one kind of region (let's call that the top-level region) but don't care to have it broken across sub-regions (let's call them the nested regions).

Or, and that's probably a more frequent use-case, you're forced for layout reasons to break into multiple regions one "visually unique" region (from the human point of view) and you may want your region break to act across those sub-regions (to the next major region) and not just trigger a break between them.

As far as I understand both specs, this is currently impossible.

My proposal is to add a region-cluster property which can take as value a comma-separated list of identifiers. When you specify "break-before: region(cluster-name)", the break occurs for the nearest parent region that has the "cluser-name" cluser name associated to it.

My second proposal is to specify that "break-before: region(all cluster-name)" means there's a break across the nearest parent region that has the "cluster-name" associated to it AND all the next sibling candidate regions that still have the same cluster name.

In both cases, if there's no parent region having the specified cluster-name, the break is ignored.

It may be necessary to allow multiple break conditions (in which case they're resolved the way they're now: we find the nearest location that satisfy all the breaks).

Any thought about that?
Received on Wednesday, 10 July 2013 21:57:36 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:29 UTC