- From: Håkon Wium Lie <howcome@opera.com>
- Date: Mon, 1 Jun 2009 15:30:00 +0200
- To: "Grant, Melinda" <melinda.grant@hp.com>
- Cc: "www-style@w3.org" <www-style@w3.org>
Melinda Grant wrote:
> > Do you have a preferred list of the values on the break-*
> > properties that would (a) provide a direct mapping from the
> > page-* properties and (b) introduce values to influence column
> > behavior?
>
> For just what we need now, for multicol, we'd suggest:
>
> break-before, -after:
> auto | column | page | right | left | avoid | avoid-page
This gives us:
Current syntax New syntax Description
page-break-before: auto break-before: auto No forced pb/cb before the element
page-break-before: right break-before: right Forced pb so that element ends up on top of right page
page-break-before: left break-before: left Forced pb so that element ends up on top of left page
page-break-before: avoid break-before: avoid pb/cb avoided before the element
page-break-before: always break-before: always pb forced before the element
break-before: page pb forced before the element
break-before: column cb forced before the element
break-before: avoid-page pb avoided before the element
ditto for *-after properties
> break-inside:
> auto | avoid | avoid-page
This gives us:
page-break-inside: auto break-inside: auto No restriction on p/c breaks inside element
page-break-inside: avoid break-inside: avoid Avoid p/c breaks inside element
break-inside: avoid-page pb avoided inside element, no restriction on c break
I like the new syntax. It is shorter and gives us the extensibility we
need to handle columns.
We would retain the current syntax for the forseeable future, but
encourage the use of break-* properties.
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Monday, 1 June 2009 13:30:43 UTC