Some devices fire a click event anyway

[alinnert]

I've noticed a very wide spread problem with touch events on some devices. It appears with every touch event library (like this one) I've tested so far as well as an own minimal solution.
It appears on the default Android browser for example, and does not appear on iOS and Chrome for Android.
It seems that an additional click event is fired right after the touch event. The problem is: the touch and the click event only share coordinates, not the tapped element.

This is a problem when you develop a "one page app" and you change the content by tapping an element. When a link appears at the exact spot where you tapped the screen that link gets triggered as well. I don't know what exactly happens, but this is, what it feels like and I don't know how to deal with this.
Does anyone know a solution to that problem?

This is not just a ask for help. If someone knows a solution it should be implemented into this script as well ;)

[jonathanstark]

@alinnert this is a known (and very annoying) issue on android. Google for "ghost click android" for the latest developments. I haven't tested for it in a while so not sure if it's still an issue or not.

[jonathanong]

should be fine if you prevent default. can you confirm?

[alinnert]

@jonathanong I'm not working on that project any longer. I can't check it. Sorry.