I've already reported this issue 21 days ago, here: #3132 and unfortunately it got tacked onto the back of another issue which resulted in it being closed. So here we go again :)

Here is an example of the problem: http://embed.plnkr.co/HQvrYQ/preview

The problem is that the tap event might have caused the DOM to change, so that the click fires in the same position but something else is there now which causes the new DOM element to incorrectly receive the event.

This issue is noticeable on iOS Safari, inside an iOS UIWebView, Android Default Browser (not Chrome) and inside an Android WebView. This does not seem to be an issue with Chrome on Android.