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 11455 [details]
A "tap" is defined as a touch down followed by a touch up after a short delay with a minimum amount of movement between the two events. That means if you put your finger down and hold it there for a long time it should not be considered a tap. Likewise, if you put your finger down and drag it across the screen it should not be considered a tap.
Currently the Xamarin.Forms tap gesture recognizes any touch down followed by a touch up on the same view. This causes problems with native gestures in ancestor views because the tap gesture is incorrectly handling gestures it should instead reject.
On iOS the UITapGestureRecognizer, on which the Forms tap gesture recognizer is built, does properly reject these non-tap gestures.
To reproduce this just open the attached solution and run the UI tests. They both pass on iOS and both fail on Android.
We implement IOnClickListener which Android docs say is "Called when a view has been clicked"...
A click is different from a tap. If you call it a tap gesture it should recognize a "tap", not a "click". A gesture detector can tell the difference. That might be a better implementation.
Indeed. A click is different from a tap and GestureDetector, amazingly enough, was the class that could tell the difference. Fix ready.
Xamarin Forms Team
Oh man, if only I could follow that link. ;)
Should be fixed in 1.4.4-pre1
I have checked this issue with X.F 1.4.4-pre2 and its working fine at my end.
Hence closing this issue.