keep header with following text

[Turtle91]

It’s called “back up coding” Jon…. Look it up.

It covers multiple devices/apps and can even cover epub 2 & 3….

You say it’s not ePub compliant, yet any device that barfs on that coding is, itself, not epub compliant… so by your logic you can’t use those devices either… bye bye ADE!! Lol

[DNSB]

Originally Posted by JSWolf

But if you are relying on webkit code, then you are doing it wrong. That's not ePub compliant and should not be used. Because you have to code for programs that do not have webkit so you may as well do that for all programs.

Jon, as per the ePub 2.0.1 specification, any unsupported properties must be gracefully degraded per the CSS 2.0 specification.

So any system that does do so is obviously not ePub2 compliant and should be dropped from discussion.

[JSWolf]

Any ePub for sale should never use code that's not ePub compliant.

[Turtle91]

Unless you are trying to compensate for all those bad apps by providing alternative coding that actually works….

[JSWolf]

Originally Posted by Turtle91

Unless you are trying to compensate for all those bad apps by providing alternative coding that actually works….

It's not compensating for bad apps. It's creating code for apps that do not use webkit and if you can create such code, then webkit is even more not needed.

[Turtle91]

“I honestly don’t know what he just said… I don’t think he does either…”

[RbnJrg]

Originally Posted by JSWolf

It's not compensating for bad apps. It's creating code for apps that do not use webkit and if you can create such code, then webkit is even more not needed.

In your previous posts, you've told us that you use BookFusion as an e-reader. Well, to manage page breaks in it, you absolutely need to use the following properties:

-webkit-column-break-after: avoid;
-webkit-column-break-before: avoid;
-webkit-column-break-inside: avoid;

If you don't use them, then it will be impossible to avoid page breaks in BookFusion. So what? Is BookFusion making a mistake by basing its rendering engine on WebKit? And BookFusion is not free.

[JSWolf]

Originally Posted by RbnJrg

In your previous posts, you've told us that you use BookFusion as an e-reader. Well, to manage page breaks in it, you absolutely need to use the following properties:

-webkit-column-break-after: avoid;
-webkit-column-break-before: avoid;
-webkit-column-break-inside: avoid;

If you don't use them, then it will be impossible to avoid page breaks in BookFusion. So what? Is BookFusion making a mistake by basing its rendering engine on WebKit? And BookFusion is not free.

If you've found out that you need to use webkit code to do page breaks, then please put in a bug report as it is a serious bug that needs to be fixed.

[RbnJrg]

Originally Posted by JSWolf

If you've found out that you need to use webkit code to do page breaks, then please put in a bug report as it is a serious bug that needs to be fixed.

No bug, is the webengine used by BookFusion. The same as Kobo for Android, Cantook, PocketBook, Reasily, Lithium, Thorium, etc. The same as the Sigil's plugin Readium, Bibi Reader and Epub JSReader.

[Slevin#7]

Don't forget Apple Books as one of the bigger eco-systems in a whole.

[Quoth]

Originally Posted by Slevin#7

Don't forget Apple Books as one of the bigger eco-systems in a whole.

Really? Apple & Google are big, but not for Apple Books or Google Playbooks.