Re: [css regions] How do regions paginate?

On 10/20/11 1:25 PM, "Vincent Hardy" <vhardy@adobe.com> wrote:

From: Alan Stearns <stearns@adobe.com>
Date: Thu, 20 Oct 2011 12:00:30 -0700
To: Adobe Systems <vhardy@adobe.com>, Alex Mogilevsky <alexmog@microsoft.com>
Cc: David Hyatt <hyatt@apple.com>, "www-style@w3.org list" <www-style@w3.org>
Subject: Re: [css regions] How do regions paginate?

Re: [css regions] How do regions paginate?
On 10/20/11 2:37 AM, "Vincent Hardy" <vhardy@adobe.com> wrote:

I guess the two options are:

a. do as you suggest and not allow regions to break. If broken, only the 'first' part of the region is ever laid out, the rest is discarded.
b. specify something similar to the multi-col spec. and deal with the more complex DOM as a result. It seems to me that we cold still have a getRegionFlowRanges on a region element. We would not know which of the region fragment the ranges are associated with, but this still seems to be a useful API. Otherwise, we could add a getRegionFragment() and the have getRegionFragmentFlowRanges() on that...

I do not have a strong opinion on where to go. I have added an issue:

http://wiki.csswg.org/spec/css3-regions?&#issue-23should-regions-be-non-breakable

May be we can resolve this at TPAC.
Thanks,
Vincent

I am assuming we should have a way of breaking regions in a paginated context (either print or screen). One of my use cases is a set of “cascading” regions that displays content in a single scrollable page, something like the first page example shown here:

http://explorationsintypography.com/about/

I’d expect to be able to print out this layout and have a region split across a page boundary, or to be able to display this page in an on-screen paginated way that split the region content at the screen page boundary.

So you are arguing for b. then, right?

Thaks,
Vincent

Yes. That option or whatever else gets us to breaking regions with a useful API.