Skip to content
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

Tapping button registers two clicks #184

Open
gRegorLove opened this issue Jan 9, 2017 · 4 comments
Open

Tapping button registers two clicks #184

gRegorLove opened this issue Jan 9, 2017 · 4 comments

Comments

@gRegorLove
Copy link

It navigates to the previous page, as desired, but acts like a double click, immediately clicking the same area on the previous page. In my app this is a user returning from a specific product view to a catalog view, and the double-click takes them immediately to another product.

HTML:
<button data-navigation="$previous-page" class="btn btn-primary fit-parent back-to-catalog"><i class="icon icon-chevron-left"></i> Go Back to Catalog</button>

It doesn't appear to be specific to the $previous-page usage, either. Same things happen if I replace data-navigation-"home" - you're taken to the homepage and a split-second later to whatever page is linked in that area of the homepage.

@gRegorLove
Copy link
Author

Forgot to add: a long-press and then release of the button makes it behave correctly.

@qathom
Copy link
Contributor

qathom commented Jan 18, 2017

Hi @gRegorLove,

Are you working with buttons only or the second button is a link button so maybe the hash of the link is used?
Did you test touch events with Chrome DevTools (or with FF) ?

@gRegorLove
Copy link
Author

gRegorLove commented Jan 23, 2017

The first is a button, the second is a regular link. This is on Phonegap (Cordova). When you tap the button, the destination page appears for a split second, but then immediately goes to whatever is linked on that page in the location you just tapped the button.

@gRegorLove
Copy link
Author

Disabling enableBrowserBackButton appeared to fix it. The behavior was happening on iOS, though, so not sure why that setting had an effect.

@qathom qathom added the v1 label Jul 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants