In that cases constructions like elem.off('tap').on('tap') makes the callback fire up twice on PC.
This will require the addition of a remove callback to the special tap event, which (imo) isn't a priority for the 1.1 release.
If you're feeling adventurous you can use @cowboy's guide to special events and submit a pull request:
That would speed things along :D. Thanks for submitting the issue.
Any updates on this? It's quite annoying that it's not possible to 'off' a 'tap' event.
this is on our list of priorities for 1.4
I have modified the tap event to support the 'off' function. I'm not sure if this is 100% the way to go with the events (first time I've been playing around with this). It works for me though.
You can see the code here: http://jsfiddle.net/w8KJv/ (I don't know how the pull request system works...)
this is fixed by commit 3ba4a42