W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [css3-break] page-break-* and break-* aliasing

From: MURAKAMI Shinyu <murakami@antenna.co.jp>
Date: Mon, 13 Aug 2012 12:07:32 +0900
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "www-style@w3.org" <www-style@w3.org>
Message-Id: <20120813120731.EC4E.C598BCD7@antenna.co.jp>
fantasai <fantasai.lists@inkedblade.net> wrote on 2012/08/13 9:47:02
> > I have one more question. I think the value 'always' and 'avoid' are
> > not necessary for page-* properties, because 'always' should be same as
> > 'column' and 'avoid' should be same as 'avoid-column'.
> > (if not in multi-column context, a column break is a region break, and
> > if not in multi-region context, a region break is a page break)
> > Is this understanding wrong?
> Well, we can't remove 'page-break' values, because they're in CSS2.1.

Sorry, I wrote 'page-* properties' by mistake instead of 'break-* properties'.

> And since column breaks and region breaks are not always the same thing
> (you can have a single region with multiple columns, or multiple regions
> within a column), 'column' and 'always' or 'avoid' and 'avoid-column'
> are not the same.

In my understanding, a page may have multiple regions or a single implicit region,
a region my have multiple columns or a single implicit column,
and a column my have anothor multi-column box inside.
In this model (page > region > column), break-*:column will be smallest 
break and will be same as break-*:always. But this may be wrong if a column 
can have multiple regions inside and those regions have no columns, 
break-*:always will be same as break-*:region in this context.

Antenna House Formatter:
Received on Monday, 13 August 2012 03:07:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:20 UTC