Quote:
Originally Posted by JSWolf
But since webkit is not part of the ePub3 spec, it should not actually be used to be ePub3 compliant.
|
I didn't understand that last statement of yours. As you know, Readium is an open source initiative whose primary goal is to facilitate the implementation of the EPUB 3 specification. Well, originally, the Readium Project (launched by the IDPF, now part of the W3C) was conceived with the idea of building its EPUB 3 reference implementation on top of WebKit. Although the direct reliance on "WebKit" as a single entity has diversified over time, the idea of using a web rendering engine to display EPUB content (which is essentially HTML and CSS) remains fundamental to Readium's functionality. So:
Readium Web: Uses the capabilities of the web browser it's running in. If your browser uses WebKit (like Safari), then Readium Web will take advantage of that.
Readium Mobile and Desktop: These native app toolkits can still use webview components, which in turn can be based on WebKit (especially on iOS/macOS) or on its derivatives/alternatives (such as WebView on Android using Blink/Chromium, or Electron on desktop using Chromium/Blink).
AFAIK, all ereaders based on Readium support webkit properties. More than that, if you want to view text in color within Calibre Viewer then you need employ the property "-webkit-text-fill-color"; without that property, no colors in Calibre Viewer. So see if the webkit properties are not important.