Quote:
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.