W3C home > Mailing lists > Public > www-style@w3.org > May 2011

RE: [css3-regions] region breaks

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Thu, 12 May 2011 10:15:26 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>, "Arno Gourdol (agourdol@adobe.com)" <agourdol@adobe.com>, "Vincent Hardy (vhardy@adobe.com)" <vhardy@adobe.com>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928411F9375E@TK5EX14MBXC218.redmond.corp.microsoft.com>
The distinction of "page" and "region" breaks is only meaningful if "page" has an exact definition.

Intuitively we may think of "page" as a sheet of paper. But when it is a paginated reading view we may say it is "top-level region"... or perhaps "the region that UI assigns a page number to"???

> What happens if one region is on page 1 and a connected region is on page
> 2?  Is that both a region and a page break?

How about this instead: region 1 is on page 2 and region 2 is on page 1 (assuming we've defined a page). What does "page break" do if it is different from "region break"?

I really think 'break-before:page' and 'break-before:region' should just mean the same. Use cases where this distinction is beneficial are rare. Cases where it is messy or ambiguous are plenty.


> -----Original Message-----
> From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
> Sent: Monday, April 11, 2011 6:13 PM
> To: Alex Mogilevsky
> Cc: www-style list; Arno Gourdol (agourdol@adobe.com)
> Subject: Re: [css3-regions] region breaks
> On Sun, Apr 3, 2011 at 4:11 AM, Alex Mogilevsky <alexmog@microsoft.com>
> wrote:
> > If region breaks should define new values for ‘break-xxx’ properties:
> > http://dev.w3.org/csswg/css3-multicol/#column-breaks instead of adding
> > separate properties.
> >
> > I am not sure there is a new kind of break though. Shouldn’t page
> > breaks consider each region a “page”? If not, and behavior of page
> > break is somehow different from region break, what is the difference?
> > Is page bigger or smaller than a region? If there is a page break
> > within a region, what does it do?
> Theoretically, you can have both page breaks within a region (if the
> region is just defined with too much height) and region breaks within a
> page (the assumed normal default).  I guess that makes it a new kind of
> break.  It should indeed work in the same framework as page and column
> breaks currently do, though, by hooking into the break-* properties.  It
> would just require a slight rewrite of the 'auto' and 'avoid' values to
> reference region breaks, and the addition of 'region' and 'avoid-region'
> values to complement the existing ones.
> What happens if one region is on page 1 and a connected region is on page
> 2?  Is that both a region and a page break?
> ~TJ

Received on Thursday, 12 May 2011 10:15:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:45 UTC