View Single Post
Old 06-17-2025, 04:52 PM   #93
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,801
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by DiapDealer View Post
I understand your reasoning on the webkit prefix stuff being tangentially related to epub3 via the systems its being rendered on, but I myself would not feel comfortable including it in an actual, for-distribution, epub's css. Only because my reading of the latest epub spec indicates that the only css prefix still a part of the spec is -epub. I'm not judging though. You do you.

https://www.w3.org/TR/epub-33/#sec-css-prefixed
I include both, standard and webkit properties. For example, if I want to force a page break, I include in the respective style:

Code:
.breakPage {
  page-break-after: always;
  break-after: always;
  -webkit-column-break-after: always;
}
Maybe can be a surprise for you but if you want to force a break in any of the Sigil's plugin (Readium, Bibi Reader, JSReader) you need to employ "-webkit-column-break-after: always" because they don't honor the standard property.
RbnJrg is offline   Reply With Quote