Quote:
Originally Posted by jugaor
Hello everyone.
I've been using both lines for many years:
Code:
page-break-after: avoid;
break-after: avoid;
(in that order) with success in all tests (except, of course, the limited Cool, FBReader, Readera, etc.).
That's why this remark intrigues me:
@RbnJrg, what devices or apps have you found that work with -webkit-column-break-after and don't honor break-after ? (I haven't found any yet.)
Since I prefer to avoid proprietary instructions (unless absolutely necessary), is this really necessary or are you just being overly protective? 
Gracias! |
All Android applications that support epub3 (Cantook, Kobo for Android, Reasily, Lithium, Infinity Reader, PocketBook, BookFusion, the old Gitden -but now is not working with modern Androids) will only honor
-webkit-column-break-after, -webkit-column-break-before and -webkit-column-break-inside. Also Thorium, Koodo Reader and ADE 4.x for PC and Foliate for Linux need those properties in order to handle page breaks.
The properties you mention are honored by ADE 2.x/3.x (ADE Legacy, that employs RMSDK), ereaders based on RMSDK and Calibre Viewer. Tolino Shine 5 needs the webkit properties. So, in order to cover al posibilities, employ always:
Code:
.noBreakAfter {
-webkit-column-break-after: avoid;
page-break-after: avoid;
break-after: avoid;
}
Y nada que agradecer
