-
Notifications
You must be signed in to change notification settings - Fork 14
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
Doesn't work when using the jquery.hammer plugin #4
Comments
I have two elements, parent and child working with tap. currently Im testing the event object in my parent for event.isTrigger === undefined. If this property isn't there I know this event is caused directly by the parent tap, if it is there, it means that the child tap event was called and I can ignore this tap on the parent. I also need to set domEvents: true on the call to the hammer plugin "hammer({domEvents: true})" for the parent (not the child); I'm not sure how reliable this is cross browser or how it would work with a child within a child, but for my current needs it works. Still it would be nice if I could use the jquery plugin and use the propagation.js |
It may work if you first load the |
Yes this worked, but it's annoying to have to load the plugin afterwards. Can't you do anything to fix this? There must be lots of people using the widget and your propagation.js |
I can think of two options:
|
How can I get this to work with the jquery plugin for hammer 2.0?
If I use the hammer plugin propagation doesn't work. If I don't use the hammer plugin hammer propagation does work with your propagation.js script
The text was updated successfully, but these errors were encountered: