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
When configuring my page to use HammerJS any element I turn a recognizer on for, will not properly handle its default events.
In safari, firefox, and the android browser nothing happens when tapping, swiping, pressing, and pinching elements for which hammer has been configured for. I know that when pinch is configured for an element it blocks it, however when I only configure tap or pan or press the same behavior is happening. On chrome only zooming and swiping is broken.
My end goal is to use hammer to simply listen for events, I don't always want to do anything other than know the event is happening.
Any help is much appreciated, I've been reading through the documentation and have not found any similar issues posted.
I've seen to been able to reduce some of the issues. However I am still having problems getting the keyboard to pop up in safari and android browser. Also enabling swipe in all directions breaks scrolling on the element, however I think that this is a known issue.
When configuring my page to use HammerJS any element I turn a recognizer on for, will not properly handle its default events.
In safari, firefox, and the android browser nothing happens when tapping, swiping, pressing, and pinching elements for which hammer has been configured for. I know that when pinch is configured for an element it blocks it, however when I only configure tap or pan or press the same behavior is happening. On chrome only zooming and swiping is broken.
My end goal is to use hammer to simply listen for events, I don't always want to do anything other than know the event is happening.
Any help is much appreciated, I've been reading through the documentation and have not found any similar issues posted.
This is the code for my page.
And the gesture.js file
The text was updated successfully, but these errors were encountered: