Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 17865 [details]
When a view has multiple TapGestureRecognizers on it, only the top level recognizer fires it's tapped event.
**Steps to Reproduce**:
1. Run the attached project on an iOS simulator
2. Tap the label in the center of the screen
3. Observe the output
Only the "Tapped 1" text is shown.
Both the "Tapped 1" and "Tapped 2" text should be shown.
**Build Date & Platform**:
I don't know if this should be filed here but when a visual element has behavior and a tap gesture recognizer the same thing happens, but the last element wins.
(In reply to John Miller from comment #0)
> When a view has multiple TapGestureRecognizers on it, only the top level
> recognizer fires it's tapped event.
> **Steps to Reproduce**:
> 1. Run the attached project on an iOS simulator
> 2. Tap the label in the center of the screen
> 3. Observe the output
> **Actual Results**:
> Only the "Tapped 1" text is shown.
> **Expected Results**:
> Both the "Tapped 1" and "Tapped 2" text should be shown.
> **Build Date & Platform**:
In the attached project, the second TapGestureRecognizer has 'NumberOfTapsRequired' set to 2; I would not expect that recognizer to fire when tapping the Label once. Is that just a typo in the repro project?
Oh, never mind John. On looking at your repro again, I see that the code in SimulGestures.cs wasn't part of the actual repro. After looking at the code in SimulGesturesXaml.xaml.cs, this appears to be a duplicate of issue 36780.
*** This bug has been marked as a duplicate of bug 36780 ***