NEW 5097
CSS2: page-break-after does not work 
https://bugs.webkit.org/show_bug.cgi?id=5097
Summary CSS2: page-break-after does not work
Niklas Janz
Reported 2005-09-22 04:20:23 PDT
Safari does not seem to support the CCS2 print styles page-break-before, page-break-after and page-break-inside. There seems to be partial support for page-break-before and -after, but no support at all for -inside. Support for these properties are crucial if you want to make a web page print in a predictable way. It is especially annoying that page-break-inside:avoid isn't supported, because that rule alone would go a long way towards making nice printouts when you don't know what font size the user will have set, or when you have dynamic content.
Attachments
3 files to demonstrate this bug (48.58 KB, application/zip)
2005-09-26 01:57 PDT, Niklas Janz 		no flags
Details
page-break-after fails in this example (15.11 KB, text/html)
2008-01-28 17:24 PST, Steve Nicolai 		no flags
Details
Simple patch to handle 'page-break-inside: avoid' in a similar manner to page-break-before and page-break-after. (891 bytes, patch)
2009-09-16 00:31 PDT, Andrew Chalmers 		no flags
DetailsFormatted DiffDiff
"page-break-inside: avoid" is ignored in Chrome (131.08 KB, image/png)
2014-02-04 10:10 PST, Dmitry 		no flags
Details
"page-break-inside: avoid" - works in Firefox 27 (192.22 KB, image/png)
2014-02-04 10:11 PST, Dmitry 		no flags
Details
"page-break-inside: avoid" - works in IE11 (107.94 KB, image/png)
2014-02-04 10:12 PST, Dmitry 		no flags
Details
reproduce "page-break-inside: avoid" problem (html+css) (41.19 KB, text/html)
2014-02-04 10:13 PST, Dmitry 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Niklas Janz
Comment 1 2005-09-26 01:57:46 PDT
Created attachment 4045 [details] 3 files to demonstrate this bug
Allan Sandfeld Jensen
Comment 2 2005-11-27 06:02:04 PST
This have now been implemented in KHTML 3.5, the patch however is quite intrusive and would probably be a lot of work to port.
Joost de Valk (AlthA)
Comment 3 2006-02-13 15:56:15 PST
Reassigning to webkit-unassigned, to make sure more people see this.
Joost de Valk (AlthA)
Comment 4 2006-02-15 14:43:06 PST
Confirmed.
Gérard Talbot (no longer involved)
Comment 5 2006-04-01 17:11:24 PST
Here's a testcase for page-break-inside: avoid: http://www.gtalbot.org/BugzillaSection/Bug132035_Page_Break_Inside_Avoid.html Safari 2.02 (416.13) fails to render that testcase correctly in Print preview.
Steve Nicolai
Comment 6 2008-01-10 18:22:10 PST
I'd like to see this bug fixed. Many of sites that print boarding passes online use page-break-* between multiple boarding passes. NWA uses page-break-after for example.
Gérard Talbot (no longer involved)
Comment 7 2008-01-10 21:33:50 PST
> Many of sites that print boarding passes > online use page-break-* between multiple boarding passes. NWA uses > page-break-after for example. " Step 3: Print your boarding pass on an 8.5" X 11" sheet of paper ...and go Straight to the Gate! " http://www.nwa.com/checkin/
Dave Hyatt
Comment 8 2008-01-11 10:40:26 PST
We support before/after mostly, but not inside. I'll retitle the bug since I assume -inside is what you're referring to. I didn't think IE supported page-break-inside though, so are sites really using it?
Steve Nicolai
Comment 9 2008-01-28 17:24:43 PST
Created attachment 18747 [details] page-break-after fails in this example Actually I was referring to page-break-after which does not work in this somewhat reduced example from the NWA site. It prints on two pages in Camino 1.5.4, but prints on one page with WebKit TOT as of Jan 26, 2008.
David Kilzer (:ddkilzer)
Comment 10 2008-02-23 13:54:29 PST
Retitling per Comment #9.
Marcin Giedz
Comment 11 2008-03-27 04:53:19 PDT
WebKit on Windows/Linux. page-break-after: always cuts very first text on next page. Here is an example code: <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> <title>TEST page-break.</title> </head> <body> <p>Page 1 of 2</p> <p style="page-break-after: always"></p> <p>Page 2 of 2</p> </body> </html> but if you add &nbsp to <p> like this: <p style="page-break-after: always">&nbsp</p> works OK. This problem doesn't exist in FF so I gather is WebKit issue. Regards
Andrew Chalmers
Comment 12 2009-09-16 00:31:22 PDT
Created attachment 39635 [details] Simple patch to handle 'page-break-inside: avoid' in a similar manner to page-break-before and page-break-after. This is a simple patch to handle the CSS property 'page-break-inside: avoid' in a similar manner to page-break-before and page-break-after. Its clear that the page-break handling required some major rework. But this might be sufficient in the mean time. I've just been using the tool wkhtmltopdf to generate documents from a project database. wkhtmltopdf uses WebKit to produce PDF file for URLs. I ran into similar issues. After a little digging, I discovered the problem is in WebKit itself. WebKit recognises page-break-inside but does not do anything with it. In fact the whole page break handling in WebKit is very limited, as is evidenced by the following comment in RenderFlow.cpp: // FIXME: This is a feeble effort to avoid splitting a line across two pages. // It is utterly inadequate, and this should not be done at paint time at all. // The whole way objects break across pages needs to be redone. // Try to avoid splitting a line vertically, but only if it's less than the height // of the entire page. Looking at how the page-break-before and page-break-after are handled in RenderBlock.cpp I put together a patch to handle page-break-inside:avoid in a similar manner. As with -before and -after -inside works only on non-floating blocks and does not deal with multiple columns correctly. But it should be sufficient until the the page-breaks are properly dealt with. wkhtmltopdf uses the WebKit verion included in the Qt source distribution. I also looked at the latest stable version of WebKit and there appears to have been no change in the page-break handling as yet. wkhtmltopdf also includes other Webkit and Qt patches that may be of interest.
David Kilzer (:ddkilzer)
Comment 13 2009-11-30 06:24:45 PST
<rdar://problem/3491400>
Yuzo Fujishima
Comment 14 2010-01-18 00:13:39 PST
As for page-break-after failure, page-break-after is applicable to block level elements http://www.w3.org/TR/css3-page/ I confirmed that WebKit - works properly for <p>, <div>, and <hr>, which are all block level elements, - but doesn't work for <span> and <br>, which are inline. Firefox 3.5.7 breaks pages for all of above. Internet Explorer 7.0 breaks pages for all except <span>. What should WebKit do?
Alex Robinson
Comment 15 2010-01-29 11:48:55 PST
(In reply to comment #12) > I've just been using the tool wkhtmltopdf Me too and loving it. However this page break issue is a real problem for being able to use it seriously (which I would very much like to do), especially since this as far as I can tell is the reason why css3 columns (aka multiple columns) can't yet be printed (bug 15546). I wish I had the chops to actually dive into this and help, but hopefully my comment might help persuade someone that fixing this would enable WebKit to be a very cool and serious print rendering engine.
Derk-Jan Hartman
Comment 16 2010-11-11 10:07:16 PST
I tried using this on headers (which are also block elements), and it does not seem as if it works there either. My layout is: <h2> <p> And I regurly have pagebreaks between the h2 element and the elements following the h2. If this is fixed, then it could greatly improve printing of Wikipedia pages.
Christophe Saout
Comment 17 2011-04-27 04:38:21 PDT
"Trivial" to fix in the new printing code: --- a/Source/WebCore/rendering/RenderBlock.cpp +++ b/Source/WebCore/rendering/RenderBlock.cpp @@ -5952,7 +5952,8 @@ int RenderBlock::applyAfterBreak(RenderBox* child, int logicalOffset, MarginInfo int RenderBlock::adjustForUnsplittableChild(RenderBox* child, int logicalOffset, bool includeMargins) { - bool isUnsplittable = child->isReplaced() || child->scrollsOverflow(); + bool isUnsplittable = child->isReplaced() || child->scrollsOverflow() || + child->style()->pageBreakInside() == PBAVOID; if (!isUnsplittable) return logicalOffset; int childLogicalHeight = logicalHeightForChild(child) + (includeMargins ? marginBeforeForChild(child) + marginAfterForChild(child) : 0); (at least that works fore me, might need some more sanity checks)
Diego Gonzalez
Comment 18 2011-06-01 07:46:02 PDT
*** Bug 36822 has been marked as a duplicate of this bug. ***
WebKit Review Bot
Comment 19 2011-08-30 07:54:41 PDT
Attachment 39635 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files']" exit_code: 1 Total errors found: 0 in 0 files If any of these errors are false positives, please file a bug against check-webkit-style.
Milian Wolff
Comment 20 2012-02-15 08:25:31 PST
The patch in comment #17 does seem to do the trick for me when it comes to "page-break-inside: avoid". It seems to resolve bug 35217, no? What would be required to get this upstream? Are there unit tests for printing? If so, I can try to write one for this, if someone can point me at some existing test code to emulate. Cheers
Gérard Talbot (no longer involved)
Comment 21 2013-03-14 16:26:32 PDT
When I load http://www.gtalbot.org/BugzillaSection/Bug132035_Page_Break_Inside_Avoid.html in Chrome 25.0.1364.172 (under Linux KDE 4.10.1, i686, 32 bits), the test is PASSED in print preview for both Portrait and Landscape page layouts. (In reply to comment #14) > As for page-break-after failure, > > page-break-after is applicable to block level elements > http://www.w3.org/TR/css3-page/ page-break-after is now break-after: " UAs that conform to [CSS21] must alias the ‘page-break-before’, ‘page-break-after’, and ‘page-break-inside’ properties to ‘break-before’, ‘break-after’, and ‘break-inside’ by treating the ‘page-break-*’ properties as shorthands for the ‘break-*’ properties (...) " 3.3. Page Break Aliases: the ‘page-break-before’, ‘page-break-after’, and ‘page-break-inside’ properties http://www.w3.org/TR/2012/WD-css3-break-20120823/#page-break and break-after still does *not* apply to inline-level elements: break-after http://www.w3.org/TR/2012/WD-css3-break-20120823/#break-after > What should WebKit do? break-after (or page-break-after) should not apply to inline-level elements. Gérard
WebKit Commit Bot
Comment 22 2013-05-06 01:23:54 PDT
Attachment 39635 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files']" exit_code: 1 Total errors found: 0 in 0 files If any of these errors are false positives, please file a bug against check-webkit-style.
hus.buy
Comment 23 2013-06-17 06:49:33 PDT
BUG: "page-break-inside: avoid" There is a bug for Chrome when div elements are in a "table". Try the code below, and you will see : - at pages 3,9 and 15: some unexpected space between first and second div; - at pages 4,10 and 16: some unexpected space between second and third div; - at pages 5,11 and 17: only 2 divs are visible instead of 3; There is a cyclic behavour every 6 pages. Thank you. ********************************************************** <html> <head> <style> table { width: 100%; } div { height: 270px; border: solid 2px; margin-bottom: 10px; page-break-inside: avoid; } </style> </head> <body> <table><tbody> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> <tr><td><div>Hello</div></td></tr> </tbody></table> </body> </html>
Gérard Talbot (no longer involved)
Comment 24 2013-06-17 11:25:22 PDT
(In reply to comment #23) > BUG: "page-break-inside: avoid" hus.buy, You most probably should be making such comment into Bug 35217 - CSS attribute page-break-inside: avoid; is not implemented. and not in here. > > There is a bug for Chrome Which version of Chrome? Under which operating system? Bug Reporting Guidelines https://www.webkit.org/quality/bugwriting.html > when div elements are in a "table". > Try the code below, and you will see : > - at pages 3,9 and 15: some unexpected space between first and second div; Can you measure such vertical gap? Or can you provide a screen shot? > - at pages 4,10 and 16: some unexpected space between second and third div; > - at pages 5,11 and 17: only 2 divs are visible instead of 3; > > There is a cyclic behavour every 6 pages. > > Thank you. > > ********************************************************** > <html> Best is to provide a test and make it accessible (attachment or make it available somewhere on the web); your test should trigger web standards compliant rendering mode and not backward-compatible "quirks" rendering mode. You can do this by starting your test like this: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> > <head> > <style> I suggest to use instead <style type="text/css" media="print"> Other points to consider: Identify - page scale (it should be 100%), - paper size (like US letter [216mm wide by 279mm tall; 8½inches by 11inches] or A4 [210mm wide by 297mm tall]) - page orientation (like Portrait) You may have (or be asked) to provide furthermore details if the problem is not reproducible: details like what are your vertical page box margins in millimeters where page header and page footer are usually printed. Vertical (and horizontal) page box margins are entirely user-settable in Chrome 27 print preview mode. > table { > width: 100%; > } > div { > height: 270px; > border: solid 2px; > margin-bottom: 10px; > page-break-inside: avoid; > } > </style> > </head> > <body> > <table><tbody> > <tr><td><div>Hello</div></td></tr> I created 2 quick versions of your test and I could not reproduce the problem you experienced with Chrome 27.0.1453.110 under Linux KDE 4.10.4, kernel version 3.8.0-25-generic, i686 (32bits). By this, I am *_not_* suggesting you are not experiencing the problem you see or that you should not report the problem you see. Gérard
Dmitry
Comment 25 2014-02-04 10:09:23 PST
The problem can be reproduced in latest Google Chrome (32.0.1700.107 m)
Dmitry
Comment 26 2014-02-04 10:10:38 PST
Created attachment 223130 [details] "page-break-inside: avoid" is ignored in Chrome
Dmitry
Comment 27 2014-02-04 10:11:36 PST
Created attachment 223131 [details] "page-break-inside: avoid" - works in Firefox 27
Dmitry
Comment 28 2014-02-04 10:12:06 PST
Created attachment 223133 [details] "page-break-inside: avoid" - works in IE11
Dmitry
Comment 29 2014-02-04 10:13:04 PST
Created attachment 223134 [details] reproduce "page-break-inside: avoid" problem (html+css)
Derk-Jan Hartman
Comment 30 2015-06-30 13:36:11 PDT
Still a problem with Safari 9 Seed1
Brent Fulgham
Comment 31 2022-07-11 17:02:54 PDT
*** Bug 35217 has been marked as a duplicate of this bug. ***
Richard Rutter
Comment 32 2025-02-14 00:04:44 PST
I see this bug didn't make it into Interop again. Any chance it could be prioritised? This has been a bug since 1997 which makes it older than some of my colleagues! The bug is harmful to understandability and the reading experience in paged media including ePubs, as well as column layout, etc.
Note You need to log in before you can comment on or make changes to this bug.