W3C home > Mailing lists > Public > www-style@w3.org > September 2006

RE: [CSS3 Paged Media] Page collapsing

From: Grant, Melinda <melinda.grant@hp.com>
Date: Thu, 14 Sep 2006 14:40:27 -0500
Message-ID: <78A3602ADF54BA4EAB53F378BF55588B22A937@G3W0067.americas.hpqcorp.net>
To: "Allan Sandfeld Jensen" <kde@carewolf.com>, <www-style@w3.org>

Hi Allan,

> I am quiet sure at least the CSS 2.1 spec clearly states that
page-breaks collapses.

Well, I'm missing it if it's there...  (That, of course, wouldn't be a
first. ;-)  Could you point me to the pertinent text?

Best wishes,


-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
Behalf Of Allan Sandfeld Jensen
Sent: Thursday, September 14, 2006 12:52 AM
To: www-style@w3.org
Subject: Re: [CSS3 Paged Media] Page collapsing

On Thursday 14 September 2006 04:39, Grant, Melinda wrote:
> Different implementations behave differently, as might be expected.  
> It seems that most implementations collapse pages.  Notably Opera's 
> does not.  I propose that the spec be made explicit 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 would make printed results more interoperable.
I am quiet sure at least the CSS 2.1 spec clearly states that
page-breaks collapses. Page break are done in margins and the value of
page-break is calculated from combining the the page-break-before and
page-break-after values of the blocks that share that margin.

Note that is somethat hard to do, so it is likely there are bugs. I know
Konqueror probably makes multiple page-breaks in your case, or at least
did in my first implementation of page-break.

Received on Thursday, 14 September 2006 19:41:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:26 UTC