Melinda,
I apologize in my delay catching up on this subject,
but Canon believes authors that accumulate multiple page-break-* properties
will do this with intent.
Collapsing valid properties is something we have not seen before, and seems
something odd to do.
Regards,
Atsushi Nakamura
Canon
Grant, Melinda wrote:
> 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> <mailto: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> _____
>>
--
Atsushi Nakamura
Senior Engineer
Inkjet Device Firmware Design 31
Canon, Inc.
3-451 Tsukagoshi Saiwai-Ku
Kawasaki JAPAN
212-8530
Tel : 81-44-542-2111 ext3713
81-44-548-7538 direct(shared)
E-mail : nakamura.atsushi318 at canon.co.jp
--