@yatish: You have to manually change the code of the function IsTouchDevice() in public.js file.
As you said, a plugin update will erase this fix and then you will have to fix it again. That’s why I emailed Tom to ask him to fix this bug for the next release.
Anyway, this is a good temporary solution before getting a fixed version of the plugin.
So I think that the issue is a false positive on the isTouchDevice check.
It is indeed. To solve the problem, I changed the code of the function IsTouchDevice() in public.js file of the plugin.
The new code looks like this:
function isTouchDevice() {
return (‘ontouchstart’ in document.documentElement && navigator.userAgent.toLowerCase().indexOf(‘chrome’) == -1); }
Now it works properly on every devices. Hope it helps.
