Hi

"avoid" only works for "page-break-inside". "always" works for both "page-break-before" and "page-break-after". "avoid" does not work for either because it needs to know exactly within what range page break should be avoided, that means it's only avoid for "page-break-inside".

Thanks

Hi,

The feature is not difficult to implement. Our main concern is logically it has to be clear and easy enough for our users to clearly understand what it does, and it has to be useful enough for sufficient amount of users so that it would be considered worthwhile for the additional complexity both from the implementation point of view and from the end user point of view. In the case of "previous" and "next" element, it's not always as clear as it looks. For example, logically the next element of a table header row would be the TBODY element instead of the next TR (because the header row is the only child of the THEAD and the THEAD’s next sibling is TBODY). Thus if you apply “page-break-after:avoid” on the table header row it will keep the whole table together instead of just putting the table header row and the next row together. This adds unnecessary confusion to our users.

Another concern is page-break-before/after: avoid is not supported on many browsers yet. We definitely do not want to go ahead of browsers because we do not lead the brower war. We follow the browsers so that our users can comfortably count on the fact that their page behaves the same in our converter as in their browsers. This is important because the absolute majority of our users have the output in their browsers first.

Thanks!

Seem that the last version of EO Pdf supports page-break-after: avoid;
Is is officially supported or just a coincidence?

Thank you very much!