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
I'm trying to verify that ng-click is indeed firing if I do not set prevetnGhosts. however my sample is not showing any ng-clicks being evented , so I checked out your demo (see link below) and it is also not showing anything for any ng-clicks. Does this mean preventGhosts is no longer needed? Or do I misunderstand the purpose?
Also, the demo does not record anything at all when tapping or clicking on the 2nd and 4th options (recognizer with prevent ghosts and stop propogation)
The text was updated successfully, but these errors were encountered:
johnpapa
changed the title
preventGhosts demo not working
preventGhosts not needed?
Mar 23, 2015
I got "ghost clicks" on hm-tap directive handlers with chrome's device emulation of "Notebook with touch". So first touchstart and touchend fire (triggering hammer's tap event) and then mousedown->mouseup->click guys come up, also triggering hammer's tap.
Though currently I can only test it in chrome's emulation (got no real device available).
I'm trying to verify that ng-click is indeed firing if I do not set prevetnGhosts. however my sample is not showing any ng-clicks being evented , so I checked out your demo (see link below) and it is also not showing anything for any ng-clicks. Does this mean preventGhosts is no longer needed? Or do I misunderstand the purpose?
http://ryanmullins.github.io/angular-hammer/examples/raw/tap
Also, the demo does not record anything at all when tapping or clicking on the 2nd and 4th options (recognizer with prevent ghosts and stop propogation)
The text was updated successfully, but these errors were encountered: