-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to determine when a tap is impossible #124
Labels
Comments
Discussed in today's PEWG call https://www.w3.org/2020/08/19-pointerevents-minutes.html. leaving this open for now to see what #123 outcome is. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some sites rely on the first
touchmove
event as an indicator that a tap is no longer possible and scrolling is about to begin. Eg. to clear a depressed state on a button from JS, or to drive custom scrolling without triggering accidentally on tap.I see that Edge sends
pointermove
events during a tap when there is a little wiggle. This must mean that pointer-event-driven carousels would sometimes wiggle when tapped. Today developers could only approximate a solution by doing their own slop suppression using some distance heuristic.Depending on the outcome of #123, we could perhaps define an event that fires when
:active
state is cleared (or a way to query whether an element is currently:active
that's better thatgetComputedStyle
).The text was updated successfully, but these errors were encountered: