View Single Post
Old 02-01-2025, 11:26 PM   #43
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: 46,600
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Aleron Ives View Post
Does the EPUB3 spec not define what a reading platform should be able to do with JS?
If you consider optional to be a directive, yes. Very little is labelled as MUST with MAY being seen all too often. If you want to play with hasFeature, be prepared to be disappointed. You can also take a look at GooglePlay which is listed as ePub3 compatible but has no Javascript support. I really recommend the ePub 3.3 specification as an insomnia cure.

Looking at the rather aged Kobo epub spec page:

Quote:
Kobo’s Android and iOS platforms support JavaScript for Fixed Layout and reflowable ePubs, but it is recommended not to use JavaScript in reflowable content in ways that may alter the layout of the book. Any EPUBs that depend on JavaScript functionality to present readable content will not pass content QA.

Kobo’s eInk and Desktop platforms have limited support for JavaScript, and do not support interactive JavaScript elements.
DNSB is offline   Reply With Quote