CSS: page-break-before "always" -- slightly wrong implementation (in PDF)

[haberbyte]

If you create an xhtml file that has a content something like this:

<style> div.chapter { page-break-before: always; }

Test

--- The generated PDF creates an empty page. The div starts at page 2. However, according to the CSS3 paged-media specs, a page-break-before: always should not create empty pages. Neither should page-break-after: always! It is correct that you always break to a new page. But creating "blank" pages is an exception to this rule. This causes some annoyances and it would be great if this gets fixed!!

[haberbyte]

Sorry, next try.

If you create an xhtml file that just has a DIV that has the CSS property "page-break-before: always". The generated PDF will have 2 pages. An empty page, and a second page with the content of the DIV.

This might seem correct, HOWEVER...the CSS3 specs say that neither page-break-before nor page-break-after properties should cause the creation of empty pages.

It would be great if this case would get fixed!

[pbrant]

Yeah, I'm afraid "empty" is not entirely trivial to detect. I think we don't create blank pages if the block element in question is right at the top of the page (with no intervening margin). 's margin might be interfering with that. It's also possible I removed that code since it was such a poor approximation of the spec.

[pdoubleya]

Moved to our official issue tracker as issue http://code.google.com/p/flying-saucer/issues/detail?id=139. Please continue discussion there.