We've been having problems at work with the tap gesture recognizer sending two events, a tap and a click, for each single tap on the screen. This seems to be a larger problem in Hammer, as its covered in the Tips page.
Jorik has created a workaround for this, PreventGhostClick, that I want to add into Angular Hammer. The simple solution seems to be to apply this functionality when the prevent_default option is set to true.
We've been having problems at work with the tap gesture recognizer sending two events, a tap and a click, for each single tap on the screen. This seems to be a larger problem in Hammer, as its covered in the Tips page.
Jorik has created a workaround for this, PreventGhostClick, that I want to add into Angular Hammer. The simple solution seems to be to apply this functionality when the
prevent_defaultoption is set totrue.