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
On touch devices, a "tap" on the touch surface will generate an emulated mouse click few millisecond later. This behavior is to reduce the potential non usability of websites that do not take into account touch interactions.
In our case, this is an issue since it doubles the number of pointer events generated. An example of this problem is testable with this JS fiddle : https://jsfiddle.net/6aw0z9hL/1/
Try a "tap" with either a touch device (smartphone/tablet) or firefox in responsive mode with touch activated.
I read that event.preventDefault() should prevent this emulated mouse event from happening but it is not the case in the example above.
The text was updated successfully, but these errors were encountered:
This prevents issue #2 from happening on smartphone but does not fix it.
Indeed, we do not want to prevent mouse events on devices that support
both touch and mouses (touch screen on laptop for example).
On touch devices, a "tap" on the touch surface will generate an emulated mouse click few millisecond later. This behavior is to reduce the potential non usability of websites that do not take into account touch interactions.
In our case, this is an issue since it doubles the number of pointer events generated. An example of this problem is testable with this JS fiddle : https://jsfiddle.net/6aw0z9hL/1/
Try a "tap" with either a touch device (smartphone/tablet) or firefox in responsive mode with touch activated.
I read that
event.preventDefault()
should prevent this emulated mouse event from happening but it is not the case in the example above.The text was updated successfully, but these errors were encountered: