- From: Håkon Wium Lie <howcome@opera.com>
- Date: Thu, 9 Apr 2009 03:02:11 +0200
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style@w3.org
Also sprach fantasai:
> 1. Introduce column-break-* as parallels to page-break-*.
> 2. Introduce break-* as shorthands that set both page-break-*
> and column-break-*.
I think this is a good proposal. It allows authors to express column
preferences using familiar values.
> But, there are disadvantages:
> - No meaningful resolution of contradictory settings like
> page-break-before: always; column-break-before: avoid;
I think we can resolve this issue by filling in a two-dimensional
array of values:
page-b-b: always page-b-b: avoid page-b-b: auto
column-b-b: always pb * cb
column-b-b: avoid pb - -
column-b-b: auto pb - -
pb = page break
cb = column break
* column break, unless it also is a page break -- in which case no break is forced
So, your example would be resolved to a page break.
> - Overhead from lots of properties that don't need to
> cascade independently and should always be set together
> anyway.
True, there are more properties than necessary. In the long run, we
may deprecate the page/column-* properties.
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Thursday, 9 April 2009 01:03:07 UTC