We agree with this proposal. We think it would better clarify page break
behavior.
***************************************************************************
Don Wright don at lexmark.comf.wright at ieee.org / f.wright at computer.org
Director of Standards
Lexmark International INCITS Executive Board Vice-Chair
C14/082-3 IEEE SA Standards Board Past Chair
740 New Circle Rd IEEE SASB Patent Committee Chair
Lexington, Ky 40550 Member: IEEE SA Board of Governors
859-825-4808 (phone) Member: IEEE CS SAB & W3C AC
603-963-8352 (fax) Director, IEEE-ISTO
***************************************************************************
"Grant, Melinda" <melinda.grant at hp.com>
Sent by: owner-xp at pwg.org
09/13/2006 10:21 PM
To: <xp at pwg.org>
cc:
Subject: XP> [CSS3 Paged Media] Page collapsing
The CSS Paged Media specification (http://www.w3.org/TR/2004/CR-css3-page-20040225/) is currently unclear as to what should happen when multiple page-break-*
properties accumulate. The spec is clear that a :left or :right
pseudo-class can require that a blank page or surface is generated.
For example:
<p>This is a paragraph on page 1.</p>
<div style="page-break-before">
<div style="page-break-before">
The first div causes a page break; does the second div cause
another page break, putting this content on page 3, or are the page breaks
collapsed into a single page break so that this is printed on page
2?</div>
</div>
Or:
<body>
<p> I am printed on the first page.</p>
<div style="page-break-after:always">
<div style="page-break-after:always">
<div style="page-break-after:always">
<div style="page-break-after:always">
<div style="page-break-after:always"> I am also printed on the
first page.
</div>
</div>
</div>
</div>
</div>
<p>Where am I printed?</p>
</body>
Or:
<body>
<p style="page-break-after">This is a paragraph on page 1.</p>
<div style="page-break-before">
The p generated a page break; does the div cause another page
break, putting this content on page 3, or are the page breaks collapsed
into a single page break so that this is printed on page 2?
</div>
</body>
Different implementations behave differently, as might be expected. I
would like to tighten up the spec to require that page-break properties
collapse such that no empty pages or surfaces are generated except for one
when needed to get to the next right- or left-facing page. Authors can
use other means to create blank pages. This will make results more
interoperable.
(I do not yet have consensus from the CSS WG to make this change. Most
implementations collapse pages, but Opera's does not, and they may not be
willing to accept the change.)
If you wish to object to this proposed clarification or express support,
please do so by posting a response here or to www-style at w3.org by September 23.
Best wishes,
Melinda
_____
HP - Melinda Grant
Connectivity Standards
Consumer Printing and Imaging
+1 (541) 582-3681
melinda.grant at hp.com
_____
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/xp/attachments/20060921/6be81316/attachment.html