Thread: Widows and Orphans
View Single Post
Old 11-13-2019, 09:18 AM   #19
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,087
Karma: 91577715
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by RbnJrg View Post
Now <h*> tags are employing BY DEFAULT the properties "page-break-after: avoid" and "page-break-inside: avoid". You won't be able to see any <h*> tags lonely at the end of a page inside a .KFX book made with KP 3.35. Even <h*> tags with multiple lines (with or without <br/> present) will be displayed together in the following page. That didn't happen before.
That matches the behavior I have observed. It is a change in the rendering of heading elements, rather than actual support for page-break-after:avoid. Publishers have no control over this and it cannot be used to avoid page breaks in general.

Added: Actually, there does appear to be a way that publishers can have a little control over this. In my testing setting widows/orphans on a heading disables the behavior of preventing a page break between it and the following text. I don't know if Amazon intended for this to happen, since none of this is documented.
Last edited by jhowell; 11-13-2019 at 09:51 AM. Reason: Add more info
jhowell is offline   Reply With Quote