New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single tap fires twice in the same location #559
Comments
Just to add to this, I have a "close" button on a modal that when you click the close (in the modal), the tap now also fires in the position underneath the modal, on the nav bar. Sounds the same kind of issue. |
I can also verify this happens with an element using ng-href in the footer bar. If you hold down the button (mouse or touch) the item fires once. If you tap it quickly, it fires twice. |
Hopefully this is a duplicate of #573, which went into the nightly build yesterday. Would you be able to test against the nightly build to see if this issue was corrected? |
@adamdbradley thank you very much! I can confirm that in the latest commit 7f9bfb5 , this problem went away. |
Awesome, thanks for double checking. |
i am getting this problem again with the following stack: Info: |
I'm getting two taps on the same location for a single tap, on the nav-bar. This happens on my iOS 6 & 7 device, and emulator. It happens in Mobile Safari, as well as UIWebView contained by cordova. I've tested this on commit 7f9bfb5 .
The code to reproduce this behavior is at http://codepen.io/anon/pen/mLrnb , however, visiting this codepen page in Mobile Safari won't trigger the bug for some reason. You have to save it locally, and serve via
http-server -p 8000
.The behavior is: When you tap the icon at top right to activate the side menu, the menu will open, but the tap is fired again on the side menu, causing another navigation (to the new page in red background). It happens not 100% of the time, but likely more than 90%.
At this point, if you click the side menu icon again to deactivate it, you can see the side menu closing up, but then another tap hit the 'back' button, which triggered another navigation back to the index page.
The two taps are fired at the same coordinate of the viewport, not the same element, leading me to think this is not a problem of my code.
The text was updated successfully, but these errors were encountered: