Created attachment 17372 [details]
Please see repro.
If you look at MainPage.xaml, you will see that I'm using a plain button, button inside a grid, button inside a stack layout, and button inside a content view. IsEnabled changes on Android do not propagate down to children.
If you tap on the buttons like a child, you will enqueue tap gestures that will be executed every 5 seconds and a datetime value will be written to the console.
iOS seems fine.
I think it is okay for children to be still enabled, so perhaps like iOS, IsEnabled changes don't have to propagate, but Grid, StackLayout, and ContentView should NOT participate in hit testing so the child button should not be clickable.
Should be fixed in 2.3.4-pre1. Thank you!
So this bug (44096) is a duplicate of the earlier reported 43007 ???
I guess the important thing is it is fixed in the new 2.3.4-pre1
I have checked this issue with xamarin.forms 2.3.4-pre1 and I have still getting same issue.
Hence reopened this issue.
Better fix: https://github.com/xamarin/Xamarin.Forms/pull/483
*** Bug 46458 has been marked as a duplicate of this bug. ***
*** Bug 43007 has been marked as a duplicate of this bug. ***
Created attachment 19927 [details]
updated repro project
This issue is still reproducible and is also affecting UWP, not just Android.
### Repro status
I'm attaching a modified project from bug #46458 that includes a UWP project.
*** Bug 53445 has been marked as a duplicate of this bug. ***
Should be fixed on 2.3.5-pre1.
*** Bug 54462 has been marked as a duplicate of this bug. ***
Still broken in 2.3.5-pre6 - yes 6.
Simple example with the scrollview disabled and the StackLayout also disabled will still allow the user to scroll up and down.
This has nothing to do with which controls the ScrollView is hosted in; ScrollViews on Android and iOS are just ignoring the IsEnabled property. It's a separate bug, fixed by https://github.com/xamarin/Xamarin.Forms/pull/1049.
Verified on xamarin.form version 22.214.171.1246-pre6. Verified on both android and UWP
ScreenCast link: https://www.screencast.com/t/YCwzSGBnMF
*** Bug 58969 has been marked as a duplicate of this bug. ***