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

Nested components cause "re"-triggering of recognizer events #73

Open
herom opened this issue Dec 13, 2016 · 2 comments
Open

Nested components cause "re"-triggering of recognizer events #73

herom opened this issue Dec 13, 2016 · 2 comments

Comments

@herom
Copy link

herom commented Dec 13, 2016

I guess I found a bug when nesting components. When each of the nested components declare a tap recognizer-event, the event will get re-triggered (in a "parent-child" nesting at least 1 time).

I created a bug-reproduction repository if you want to see what I mean 👍

@herom
Copy link
Author

herom commented Dec 14, 2016

When using the tap recognizer, I always get 2 events shortly after another (~1ms). Both of them show that they are "tap" events, the second one shows a tapCount of 2 (tested on Windows with Chrome latest, IE11 and Apple iPad iOS 10.1.1 mobile Safari).

If I use the single-tap recognizer instead of the tap recognizer everything works like expected. Why?

@jdurand
Copy link

jdurand commented Jul 26, 2017

I'm experiencing a similar issue. I had an outer component using tap and an inner component using tap doubleTap. A tap or a click on an element in the inner component triggers the action twice (tried bubbles=false, same thing).

Removing tap from my inner component fixes the issue, but seems to conflict with using doubleTap on the outer component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants