On most Microsoft UI platforms such as Silverlight, WPF, and UWP, if an element's IsEnabled property is set, this cascades down through the Visual Tree. This does not seem to be the case in Xamarin Forms. Why not? I consider this a bug. When will this be fixed?
Here is an example:
<?xml version="1.0" encoding="utf-8" ?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" x:Class="TestXamarinForms.IsEnabledPage" IsEnabled="False">
<ContentPage.Content>
<Grid x:Name="TheGrid" IsEnabled="False">
<Button Text="Test" />
</Grid>
</ContentPage.Content>
</ContentPage>
Clone this repo:
git clone https://ChristianFindlay@bitbucket.org/ChristianFindlay/xamarin-forms-scratch.git
Run the app on UWP or Android, and click the IsEnabled Cascading button. Notice that the button is enabled despite its parents being disabled.
I would expect the button above to be disabled because its parents are disabled. But, this button is enabled. If I were to log this as a bug, would it get fixed?