For my purposes, the limited implementation of JS in the Kobo WebKit based renderer is moderately useful but 99.99% of the ebooks I've seen do not use JS at all. I also remember that Kobo's ereaders are intended for reading ebooks. Most of the features of JS are less than useless for reading ebooks. Implementing features that would not be useful for ebooks is not laziness, it's more likely that the programmers are trying to keep the code size down for a device with limited memory and CPU.
Quote:
Originally Posted by mramosch
On iOS you can use event.preventDefault() to break through this filter and get to your underlying JS code for providing the user with further interactive functionality.
Only on the KOBO device itself you can’t…
|
I am curious as to what layer below the renderer on a Kobo ereader are you trying to send touch events to? The Linux OS? Have you written a shim to run between the renderer and Linux?