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
Nonetheless, I am trying to make significant improvements to event-tap, to bring it up to par with some of the other fastclick implementations out there.
This ticket will specifically reference making sure event-tap works as expected across the board (but especially in Android 4.0.x (in both, Chrome and the default Android browser)).
The text was updated successfully, but these errors were encountered:
I would like to group this fix along with the dual-listener work, because they are related. I have a dual-listener branch on my yui3 fork. Currently, the default Android browser fires touch and mouse events, and tap callback gets fired twice. Chrome on Android only fires touch events. Looking into fixing this by having event-tap detaching mouse event handles if the touch event callbacks are fired.
This issue references Trac #2532915. I have tested this fiddle on Android 4.0.3 and it seems to work for me. Waiting to hear back from @mschipperheyn.
Nonetheless, I am trying to make significant improvements to event-tap, to bring it up to par with some of the other fastclick implementations out there.
This ticket will specifically reference making sure event-tap works as expected across the board (but especially in Android 4.0.x (in both, Chrome and the default Android browser)).
The text was updated successfully, but these errors were encountered: