-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Meta] Fastclick, Inputs, and "Ghost Clicks" #808
Comments
Potentially would fix this issue: #578 |
This occurs because ghost clicks don't maintain the original target, only the coordinates: #411 |
For anyone tracking this issue or the related ones we have created a new fast click to avoid using tap for a fast click. https://github.com/hammerjs/hammer-time this is very much still alpha but should be very sound based on testing. |
Fixes determination of if it is acceptable to prevent the browser default behavior of scrolling/zoom etc when the touch-action property is set to none and the browser does not provide native support for the touch-action property. It fails to differenciate between a tap gesture and a multi-touch gesture which results in click and hover events from not getting recognized when an element has multi-touch gesture associated with it. Ref #838 Ref #808 Closes #762
im going to close this i dont think it is relevant any longer |
I'm having the same issue as #411 with hammer 2.0.8 using it with Angular 4 |
same as above 2.0.8 and Angular 4 |
This is a meta issue for problematic click behavior that will largely be dealt with by converting to pointer events.
Affected Issues:
The text was updated successfully, but these errors were encountered: