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 for Bug 39472 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 15321 [details]
Sample project attached which demonstrates issue
## Steps to reproduce
1. Download attached sample
2. Build All and run on iOS/Android
3. Try to click the button
## Expected result
Opacity of 0 allows tap events to pass through, acting as though you'd set the control invisible
## Actual result
As expected, opacity of 0 allows tap events to pass through
The fully transparent layout will block all events. To work around if you're setting a control to 0 opacity, you need to on android set the view invisible too.
For example you might be animating the fading of a view out. On Android you currently have to remember to also set it invisible once the fade is done. You don't have to do this on iOS.
When you fade the view back in you need to set it Visible first on Android.
Yeah this is a known distinction between how these platforms handle input
I worked on a different problem: https://github.com/xamarin/Xamarin.Forms/pull/344
Not sure if it would have any affect on this problem. You probably need to re-test once the PR is merged.