View Single Post
Old 01-15-2026, 09:00 PM   #34
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 50,734
Karma: 178402706
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
Why would the renderer require webkit code if it's written properly to support ePub3? It should not need to. And besides, it's not valid code. It's not part of any ePub spec.
There are quite a few ePub renderers out there. Some of them still use the -webkit extensions. It's simply easier for me to allow for their existence than to threaten to hold my breath until I turn purple if the renderer is not upgraded to a version that does not need the -webkit extensions.

As for not being part of any ePub spec? Not that big a concern to me since I've found virtually all renderers treat a properly structured but unknown entry in a CSS stylesheet as a null operation.
DNSB is offline   Reply With Quote