Fix SafeAreaEdges comments and access modifiers

[jeremy-visionaid]

Layout.SafeAreaEdges documents the default value to be "None", but the default value delegate actually returns "Container".

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 34397

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 34397"

[Copilot]

Pull request overview

Updates XML documentation for SafeAreaEdges defaults across several Controls types to better reflect current safe-area behavior and to standardize wording.

Changes:

• Adjusts documented default safe-area behavior for Layout, ContentView, ContentPage, and Border.
• Standardizes “edge-to-edge” wording in the ScrollView safe area docs.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/Controls/src/Core/ScrollView/ScrollView.cs	Doc wording tweak for the SafeAreaEdges default description.
src/Controls/src/Core/Layout/Layout.cs	Updates documented default SafeAreaEdges value for Layout.
src/Controls/src/Core/ContentView/ContentView.cs	Updates documented default SafeAreaEdges value for ContentView.
src/Controls/src/Core/ContentPage/ContentPage.cs	Updates documented default SafeAreaEdges value for ContentPage.
src/Controls/src/Core/Border/Border.cs	Updates documented default SafeAreaEdges value for Border.

Comments suppressed due to low confidence (2)

src/Controls/src/Core/ContentView/ContentView.cs:42

• The remarks for SafeAreaEdges refer to SafeAreaRegions.Keyboard, but SafeAreaRegions does not define Keyboard (it uses SoftInput). Please update the remarks to use the correct enum value name (and ensure the guidance matches the actual values supported by SafeAreaRegions).

		/// The default value is SafeAreaEdges.None (edge-to-edge).
		/// </summary>
		/// <remarks>
		/// This property controls which edges of the content view should obey safe area insets.
		/// Use SafeAreaRegions.None for edge-to-edge content, SafeAreaRegions.All to obey all safe area insets, 

src/Controls/src/Core/Border/Border.cs:70

• The remarks for SafeAreaEdges mention SafeAreaRegions.Keyboard, but SafeAreaRegions doesn't have a Keyboard value (it uses SoftInput). Please update the remarks to use the correct enum value name so consumers aren't pointed at a non-existent option.

		/// The default value is SafeAreaEdges.None (edge-to-edge).
		/// </summary>
		/// <remarks>
		/// This property controls which edges of the border should obey safe area insets.
		/// Use SafeAreaRegions.None for edge-to-edge content, SafeAreaRegions.All to obey all safe area insets, 

---

You can also share your feedback on Copilot code review. Take the survey.

[jfversluis]

@jeremy-visionaid I see Copilot has some minor comments. Can you please double-check and let me know? :)

[jeremy-visionaid]

@jfversluis This maybe opens up a can of worms... 😅

I'd probably accept Copilot's first suggestion - even though it was the thing that wrote it in the first place. ScrollView behavior is special, so it doesn't map cleanly to the abstracted values.

It's not wrong about the internal reference, but it also implemented that incorrectly too. e.g.

	/// <summary>
	/// A <see cref="SafeAreaEdges"/> with all edges set to <see cref="SafeAreaRegions.All"/>.
	/// </summary>
	internal static SafeAreaEdges Container { get; } = new(SafeAreaRegions.Container);

The comment is incorrect, and it's internal, when it should probably be public. It is the value that's actually used as a default (you can only create an equivalent struct and not use that member directly). It is referenced from the MAUI docs (which also incorrectly refer to it as an enum):
https://learn.microsoft.com/en-us/dotnet/maui/user-interface/safe-area?view=net-maui-10.0#safeareaedges-enum

For the scope of this PR, I was only intending to address the thing that caught me and another team member out - the behavior of the controls wasn't what we expected since IntelliSense told us the wrong defaults. There's prob more AI slop that needs fixing after this - there was a bunch of stuff that looked off to me but I didn't know where I should stop 🤷 I think it's reasonable to fix up the SafeAreaEdges.Container bit here too, but it does affect the public API...

[jeremy-visionaid]

@kubaflo I've changed it to satisfy Copilot, and added a few other bits that it missed. Unfortunately, the comments also reference members that appear to be unintentionally internal, so it also needs an update to the public API...

[kubaflo]

@PureWeen what do you think?

[PureWeen]

retarget to net11.0

Otherwise looks good

[MauiBot]

⚠️ Merge Conflict Detected — This PR has merge conflicts with its target branch. Please rebase onto the target branch and resolve the conflicts.

[kubaflo]

@jfversluis we can merge this to net11

The base branch was changed.

[dotnet-policy-service]

🚨 API change(s) detected @davidbritch FYI

[dotnet-policy-service]

🚨 API change(s) detected @davidortinau FYI