Tap firing twice

[MadhuSudhanBhaskar]

I am using Angularjs, for events I am using hammer.js . I have a new version on hammer.js on my application. The tap is binded my directive, when I tap or touch on my mobile device its firing twice.

[RyanMullins]

@MadhuSudhanBhaskar I'm the maintainer of Angular Hammer and have been encountering a similar problem. When you get a chance, take a look at my issue (#742) , which details what we believe to be the problem, and compare with your own code/experience. If you find it to be the same I would recommend closing this issue and watching my issue.

[runspired]

@RyanMullins Did you miss the part of the docs that suggests preventGhostClicks?

http://hammerjs.github.io/tips/

https://gist.github.com/jtangelder/361052976f044200ea17

[RyanMullins]

Nope. Please read the details of my issue. It's a very different problem related to capturing both TouchEvents and MouseEvents fired from a single click but milliseconds apart.

[RyanMullins]

@runspired Unless I'm completely misinterpreting the point of PreventGhostClicks, which I view as a way to stop other handlers from being fired when after a Hammer handler responds.

[RyanMullins]

@runspired this may even be a problem particular to Angular. If it is, it's because of the Angular execution context where it effectively adds a second run loop inside of the JavaScript run loop, so it could be that the secondary mouseup event is being triggered before the PreventGhostClicks functionality in the Angular context has a chance to respond. If that is the case, then the solution I want will eliminate the need for PreventGhostClicks.

[runspired]

@RyanMullins I think you are misinterpreting PreventGhostClicks, but I agree it should be bundled with Hammer and used by default. Basically, mobile browsers try to pretend that they are normal browsers, so they fire a "click" event a short delay after a "touchEnd". This is great for sites that haven't optimized for mobile, but for sites that do use touchEnd to determine taps/clicks, the extra click event needs to be captured and discarded, otherwise both the touchEnd and the click event will trigger a tap.

[RyanMullins]

Sounds like I know what I'm working on tomorrow afternoon then.

[MadhuSudhanBhaskar]

@ryan Sure I will check your issue and close mine.
On 08-Jan-2015 3:53 am, "Ryan S Mullins" [email protected] wrote:

Sounds like I know what I'm working on tomorrow afternoon then.

—
Reply to this email directly or view it on GitHub
#727 (comment).

[runspired]

Closing in favor of the meta issues for this.