I know some people are fans of epub3, evangelists for it, but:
1) Only a subset of Javascript works on epub3.
2) Only a tiny number of apps fully support epub3
3) The majority of physical ereaders have very little or no epub3 support.
4) The majority of physical ereaders (inc Kindle) have little or no javascript support
5) A real ebook doesn't need any Javascript shouldn't use any.
6) Javascript execution creates a possible malware vector.
Quote:
|
ADE 4.5x, Thorium (for Linux and Windows), Koodo Reader (for Linux and Windows), Foliate (Linux), Sigil and its plugins Readium, Bibi Reader and EpubJS Reader, Calibre Viewer and Calibre Editor, EpubReader (for Chrome and Firefox), ePUB Reader (for Chrome and Firefox), PocketBook, Gitden Reader, Reasily, Lithium, Aldiko Next, Overdrive, Bluefire Reader, BookFusion, Infinity Reader (all Android apps). All this programs and apps support javascript practically "in totum".
|
Some of these are used by a minority of people reading.
If you really need interactive (the reason for Javascript) consider a framework to produce iOS and Android apps. This of course can't sell via the ebook stores that sell about 99% of ebooks, but most of those won't distribute ebooks with Javascript (Amazon).
I've Aldiko, Bluefire, Lithum and Pocket Book on Android. I've about 500 bought ebooks (since 2013 and from four stores) and about 5,000 PD ebooks (since about 2002). Not a single ebook has Javascript. Not a single ebook was delivered or downloaded in epub3.