The browser that supports pointer event, The Hammer doesn't work.
See original GitHub issueChrome has began supporting PointerEvent
since version 55.
If you don’t set inputType
on Hammer.manager, Hammer use Pointer Event as a InputType.
But, Hammer.js has bug about Pointer Event. The Hammer doesn’t work anything.
related issues
#1082, #1071, #1068, #1067, #1065, #1058, #1056, #1054, #1048
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
372357 - Scrolling broken due to touch-action support on sites ...
Issue 372357: Scrolling broken due to touch-action support on sites using hammer.js library (eg. currys.co.uk). Reported by schedule owale@chromium.org owale ...
Read more >Dragging an element with hammer.js fails on mobile
In a desktop browser it works, but on mobile when I start dragging it works briefly, then suddenly acts as if the event's...
Read more >API - Hammer.js
Unbinds all events and input events and makes the manager unusable. It does NOT unbind any domEvent listeners. Hammer.Recognizer. Every Recognizer extends from ......
Read more >CSS pointer-events (for HTML) | Can I use... Support tables for ...
This CSS property, when set to "none" allows elements to not receive hover/click events, instead the event will occur on anything behind it....
Read more >Gestures in an Angular Application - InDepth.Dev
ts file you will see an error within the console that will stop your application from running. <>Copy. Error: Hammer.js is not loaded,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Here is an easy-peasy solution (no need to modify the library code):
I tested in with Hammer 2.0.8 on Chrome (Mac), Safari (Mac and iOS 13) and iOS 13 webview.
You can add the following code to the end of the
assign(hammer, {
… section in v2.0.8 (at the end):Then, call
Hammer.supportPointerEvents(false);
on app startup (before adding instantiating items). This will effectively turn the pointer-events processing off; and make many of these problem go away (for now anyway).