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

Open
RByers opened this Issue Jul 29, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@RByers
Contributor

RByers commented Jul 29, 2016

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 that getComputedStyle).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment