SafeAreaEdges Seems to Do Nothing

[david-maw]

Description

Explicitly setting SafeAreaEdges to None" on a ContentPage does not seem to have any effect. Running on an Android 36 emulator I'd expected to see the top line of my form immediately next to the screen edge, behind the Android status bar. Instead, I saw this:

Which is what I'd have expected if SafeAreaEdges was set to pretty much any other value.

Steps to Reproduce

1. Clone the repo
2. Build and run the app on Android 36
3. Observe the alignment at the top of the page.

Link to public reproduction project repository

https://github.com/david-maw/SafeAreaEdges.git

Version with bug

10.0.40

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Android, I was not able test on other platforms

Affected platform versions

Android 36 was all i tested

Did you find any workaround?

No

Relevant log output

[sheiksyedm]

@david-maw To achieve your scenario, the Grid is also explicitly set to SafeAreaEdges="None" because layouts default to Container. Refer to the documentation for more details.
https://learn.microsoft.com/en-us/dotnet/maui/user-interface/safe-area?view=net-maui-10.0#edge-to-edge-content

[dotnet-policy-service]

Hi @@david-maw. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[david-maw]

Got it, thanks @sheiksyedm, I was working from the release announcement and naively assumed an explicitly specified value would override default settings in nested objects. Looking at the examples in the documentation I can't see how setting SafeAreaEdges at the ContentPage level is ever useful since most embedded controls will override it - so the documentation could perhaps use a bit of work. Nevertheless, this solves my problem, so thanks.