View Single Post
Old 07-11-2016, 07:31 AM   #15
Phssthpok
Age improves with wine.
Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.
 
Posts: 584
Karma: 95229
Join Date: Nov 2014
Device: Kindle Oasis, Kobo Libra II
Quote:
Originally Posted by dgatwood View Post
if you can wrap the two pieces of content in a div and mark that with page-break-inside: avoid, you should usually prevent the break without forcing a break before the first item, provided that:
  1. Neither the enclosing div nor the content inside it uses position: absolute or position: fixed
  2. The content of the enclosing div can fit on a single page
  3. None of the interior elements expand to fill the screen
  4. The enclosing element is a block element (not inline or inline-block or table-*)
  5. The enclosing content is not inside a table (known WebKit bug)
I'll try this. If it works more often than it does now (i.e. if it works even once), it's an improvement.

All the same, it seems odd that "avoid" is basically ALWAYS ignored of page-break-after. I would have thought "keep with next (where feasible)" would be a sensible interpretation; oh well. Yes, I know it's only advice, but even my mother's advice wasn't ignored that consistently...

Thanks!

Last edited by Phssthpok; 07-11-2016 at 07:36 AM.
Phssthpok is offline   Reply With Quote