- From: MURAKAMI Shinyu <murakami@antenna.co.jp>
- Date: Sun, 24 Jan 2010 19:34:08 +0900
- To: www-style@w3.org
- Message-Id: <20100124193408.86BC.C598BCD7@antenna.co.jp>
Hi, Yuzo Fujishima <yuzo@google.com> wrote on 2010/01/22 11:02:53 > Suppose that > there is a block-level element just before the end of body > and that > the element has page-break-after:always property. > (See an example below.) > > Should the pages break there? In other words, should a content-empty page > follow the penultimate page? > > http://dev.w3.org/csswg/css3-page/#forced-pg-brk says: > no content-empty pages are generated by page-break properties, except for > at most one content-empty page as may be required by ‘right’ and ‘left’ > values to position ensuing content on a right- or left-facing page. > > Although the above line is for when multiple page-break-* properties apply > at a margin, > it seems to be a good general guideline. > > I believe vast majority of users don't want a content-empty page at the end. I agree with you. I also believe the page-break-before:always should not generate a blank page at the beginning of a document. I tested some implementations: AHFormatter = Antenna House Formatter 5.1 Prince = Prince 7.0 PDFreactor = PDFreactor 4.0 IE = IE8 (print preview mode) Firefox = Firefox 3.6 (print preview mode) Opera = Opera 10.10 (print preview mode) Safari = Safari 4.0.4 (print preview mode) Chrome = Chrome 4.0.249.78 (print) 'page-break-after:always' generates a blank page at the end? AHFormatter: No Prince: No PDFreactor No IE: No Firefox: No Opera: Yes Safari: Yes Chrome: Yes 'page-break-before:always' generates a blank page at the beginning? AHFormatter: No Prince: No PDFreactor No IE: No Firefox: Yes Opera: Yes Safari: Yes Chrome: Yes (test files are attached) -- Shinyu Murakami Antenna House Formatter team http://www.antennahouse.com
Attachments
- text/html attachment: break-after.html
- text/html attachment: break-beforer.html
Received on Sunday, 24 January 2010 10:35:05 UTC