SafeAreaEdges.Container is not accessible

[dartasen]

Description

Looking at Safe Area documentation to migrate an app to .NET 10, I notice that SafeAreaEdges.Container is hinted as "equivalent behavior" as .NET 9, so it looked good to me.

However it's not accessible at all from code-behind.

Steps to Reproduce

N/A

Link to public reproduction project repository

No response

Version with bug

10.0.60

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

No response

Affected platforms

iOS, Android, Windows, macOS

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

[Ahamed-Ali]

This issue has been validated in Visual Studio Code 1.120.0 with .NET MAUI versions 10.0.0, 10.0.30, 10.0.51, and 10.0.60. The issue was reproducible

[SyedAbdulAzeemSF4852]

SafeAreaEdges.Container is currently marked as internal, so it cannot be accessed directly from application code. However, SafeAreaEdges provides a public constructor that accepts a SafeAreaRegions value, and SafeAreaRegions.Container is publicly accessible. As a workaround, the equivalent value can be created using the public API:

var container = new SafeAreaEdges(SafeAreaRegions.Container);

This produces the same result without requiring direct access to SafeAreaEdges.Container.