You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the following simple scenario I created there are different events fired when using the plugin versus not using this plugin.
Here is the following code to reproduce - I've moved everything related to Cordova to a single html file:
This basically draws the events that are captured from the canvas to a ul element.
When not using the plugin the only event that are fired when using long click are: touchstart and touchend
When using this plugin there are more event related to mouse operations which shouldn't be fired: touchstart touchend mousemove mousedown mouseup
I think this is new, maybe in 15.4 or so as I think this was not present in 15.0.
It happens only on "long click" and not on "regular click".
Please let me know how I can help further debug this issue.
I have removed this plugin from my code and saw that the issue is resolved.
But this created the unwanted situation where local storage is lost due to scheme and host name changes.
Is there an easy way to keep the local storage but still remove this plugin?
i.e. set in android something like:
In the following simple scenario I created there are different events fired when using the plugin versus not using this plugin.
Here is the following code to reproduce - I've moved everything related to Cordova to a single html file:
This basically draws the events that are captured from the canvas to a
ul
element.When not using the plugin the only event that are fired when using long click are:
touchstart
andtouchend
When using this plugin there are more event related to mouse operations which shouldn't be fired:
touchstart
touchend
mousemove
mousedown
mouseup
I think this is new, maybe in 15.4 or so as I think this was not present in 15.0.
It happens only on "long click" and not on "regular click".
Please let me know how I can help further debug this issue.
The text was updated successfully, but these errors were encountered: