Quote:
Originally Posted by fbrzvnrnd
Thank you for the answer. I used the specification you linked to, but the problem is here: "Kobo’s eInk and Desktop platforms have limited support for JavaScript, and do not support interactive JavaScript elements. "
I tried and Kobo's e-ink *supports* interactive elements... but it fails to disable the touch for turning page and menu on/off...
|
I can think of two things here:
- Kobo's statement of what it supports doesn't say that the Javascript isn't executed. You can probably take it as "doesn't necessarily work the way you want". As Kobo uses ACCESS (or whatever it is called now) for kepubs, and that uses WebKit or something like that, unless Kobo has explicitly blocked something they support, then you will see mixed function like this.
- It's possible you need to do something else to indicate the event has been consumed and isn't to be passed on to the next consumer. In other windowing environments, I have done this by setting a flag or it is based on the return value of the function. I have no idea what this would be in this case.
Also, there is a page somewhere that tests ereaders and apps for epub3 support. This lists what the Kobo ereaders do support from their testing. Finding that and seeing what it says might give you an idea of what can be done.