Quote:
Originally Posted by jugaor
—Google Play Books (not in your list) is almost a must for our student audience, often with Android tablets/phones, who prefer its notes and multi-device sync capabilities.
|
Ahhh, I see you are working under epub2. I didn't have GPB in the list I posted because GPB doesn't support epub3 and I believed you were working under that protocol.
The "bug" you were watching under Reasily, Lithium, etc. is due those apps "understand" (because of the properties break-before: column and -webkit-column-break-before: always) that one is working with multi-columns and so, they apply the default value for the property column-fill, that is, "column-fill: balance".
Quote:
|
Sadly, your recommended order prevents the page jump from working. My idea of using @supports is to "hide" that part, so GPB only uses the first page-break.
|
It's ok; since GPB works only with epub2, you don't need -webkit-column-break-before or break-before. Those are properties from css3. With page-break-before is enough for GPB. Of course, if you also need to do compatible your ebook with Reasily, Pocket, Lithium, etc., etc., then you'll do need the css3 properties and the use of @support is a right way to do the things.
Quote:
—In the apps I have been able to test it seems redundant to use -webkit-column-break in addition to the canonical break (see PDF table).
Please can you point me which applications/readers require the former as mandatory?
|
So far, all the apps and programs of my list, don't need -webkit-column-break-before EXCEPT the Sigil plugins: Readium, Bibi and EpubJS. The potencial issue is that many apps are starting to use the Readium engine, and then they could need the -webkit property to force a page-break. So, I include "-webkit-column-break-before: always" just in case.
Nada que agradecer, acá estamos para aprender todos de todos.