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.
If a view has a null background, it (the background) will not be hit-tested and will not trigger a TapGestureRecognizer on Windows Phone. (as a opposed to a transparent background, which *will* still receive taps)
However, this is not the behavior on iOS... the view will receive taps regardless of the background color.
These are both standard behaviors for their platforms (I don't know what Android does), but Xamarin Forms should have a more consistent behavior across platforms in this regard.
(I would personally prefer the Windows-style behavior, as you could then achieve the iOS-style behavior by using a transparent background, whereas getting iOS to have the Windows-style behavior requires a custom renderer.. but the point is that it should be consistent either way)
I have tried to reproduce this issue and not able to reproduce it.
Could you please provide us sample project? so that we can reproduce it at our end.
Created attachment 12864 [details]
Here is an extremely simple sample project. On iOS, taps will be registered in the output window wherever you tap. On WinPhone, they will only be registered when tapping on the label.
Still occurs in 188.8.131.5229
We have had other bugs filed that are related to this issue but I believe our consensus was that this sort of behavior was to stay in place. Setting background colors explicitly is a performance loss. If the documentation involving this behavior has not been updated it is something that could be in the future.