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 21188 [details]
Solution demonstrating the problems
IsEnabled does not propagate recursively down the view hierarchy correctly on Android.
The attached sample solution includes the following view hierarchy:
On iOS, setting IsEnabled on the ContentPage prevents clicking the nested button. On Android, setting IsEnabled on the ContentPage does not prevent clicking the nested button. In my opinion, the iOS behavior is correct, and the Android behavior is not correct.
Tested on Xamarin.Forms version 18.104.22.168, iPhone 7 Plus 10.3 simulator, Intel Atom (x86) Android 6.0 API level 23 emulator.
At minimum, the documentation at https://developer.xamarin.com/api/property/Xamarin.Forms.VisualElement.IsEnabled/ should be updated to tell how IsEnabled behaves on each platform.
*** This bug has been marked as a duplicate of bug 44096 ***