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
As a rule of thumb, the click delay occurs when the default action is handled by the browser. In other words, the click delay is suppressed when the application cancels the default action.
Here is what happens when you touch the screen on IE10+ (with Pointer Event). This is just an observation because the click behavior is not part of the Pointer Events specification:
there is a delay if touch-action on the target element determines that the browser handles the default action (that is the default behavior and is equivalent to set touch-action=auto).
The delay is suppressed when you specify touch-action=none.
touch-action=pan-y
It lets the browser handle the default action when user scrolls vertically (no Click event in that case)
If user just Tap, or moves its finger horizontally, a click event comes immediately with no delay.
dpointer acts the same:
when it doesn't prevent default action on touch events, a click will happen with a delay.
when it prevents the default action (essentially by calling |preventDefault() on the first touchmove), it will synthesize and send a click with no delay.
(I mentioned this as a comment in google doc, but adding here before I forget.)
Dpointer has code to eliminate the 300ms click delay on webkit (i.e. platforms supporting touchstart/touchend), but IIUC not for IE10 or IE11.
I didn't try personally, but @edurocher wrote how IE also has a click delay, so please doublecheck if this is working w/out a delay.
The text was updated successfully, but these errors were encountered: