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.

[JSWolf]

Originally Posted by RbnJrg

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.

Sure it's the web engine used, but you should not have to use any webkit code for anything. Anything you need to use WebKit for because ePub code isn't working is a bug that needs to be reported so it can be fixed.

[RbnJrg]

Originally Posted by JSWolf

Sure it's the web engine used, but you should not have to use any webkit code for anything. Anything you need to use WebKit for because ePub code isn't working is a bug that needs to be reported so it can be fixed.

Thus, and following your reasoning, it's also not legal to use any of the workarounds for ADE, because it doesn't comply with the epub2 specifications. Using a WebKit property is, if you will, a workaround, which doesn't cause any problems for e-readers that don't understand the property. Because of the way these engines paginate an .xhtml file (they turn the entire page into columns), there's no other way to handle page breaks other than using -webkit-column-break-whatever.

Employing a -webkit- prefixed css property in an epub doesn't inherently constitute a "bug" in the sense of a coding error. The best practice for epub is to use standard css properties whenever possible, and to include vendor-prefixed versions as fallbacks where the standard equivalent is not yet fully implemented or consistently supported across all target ereaders.

[JSWolf]

Originally Posted by RbnJrg

Thus, and following your reasoning, it's also not legal to use any of the workarounds for ADE, because it doesn't comply with the epub2 specifications. Using a WebKit property is, if you will, a workaround, which doesn't cause any problems for e-readers that don't understand the property. Because of the way these engines paginate an .xhtml file (they turn the entire page into columns), there's no other way to handle page breaks other than using -webkit-column-break-whatever.

And she the WebKit code is ignored, whatever it is you are trying to do won't work.

What ADE workarounds are not compliant with ePub2?

[RbnJrg]

Originally Posted by JSWolf

And she the WebKit code is ignored, whatever it is you are trying to do won't work.

If what I'm trying is to handle page-breaks and if the engines are based on webkit, then -webkit-column-break-whatever will be accepted. OTOH, if the engines are not based on webkit, will employ the properties "break-whatever" (epub3) or "page-break-whatever" for RMSDK.

What ADE workarounds are not compliant with ePub2?

For example, to employ emojis as name of a class. Under ADE is possible to use an style of the following way:

.👻 {
...
}

That class will be ignored by any other engine that is not using RMSDK, so of that way, you can have styles only to be applied by ADE. You can apply custom styles to fix issues unique to ADE that are ignored by any other reader not based on RMSDK.