Revert default for UseSafeAreaProperty to value from .NET 6 for iOS

[hartez]

Description of Change

#10083 modified the default value for the UseSafeAreaProperty; this change sets it back to the original value from .NET 6 for iOS.

This should be backported for 7 since the original PR caused a behavior change in 7.

Issues Fixed

Fixes #12823

[Eilon]

Tagging @tj-devel709 - you were looking at something similar recently.

[rachelkang]

yay regression fixing! I'm curious though; why did changing the default break the property entirely?

[PureWeen]

PageAdjustsWhenTopTabsArePresent

Is currently failing on iOS

[hartez]

yay regression fixing! I'm curious though; why did changing the default break the property entirely?

It didn't.

There are two properties in play - UseSafeArea (on Page) and IgnoreSafeArea (on Layout). In .NET 6, UseSafeArea was false by default, which meant that the Page would lay its content out in the entire screen (even behind the notch). So the value a user set for IgnoreSafeArea made a difference. In .NET 7, the default for UseSafeArea changed to true, which meant that the Page constrained all of its content to the safe area; you could tell a Layout on the Page to ignore the safe area, but it didn't matter because it was already entirely within the safe area.

So you might have a Page in .NET 6 with a Grid marked IgnoreSafeArea = true, and that Grid would layout behind the notch. Then you'd move to .NET 7, and the Grid would stop laying out behind the notch. It looks like IgnoreSafeArea is busted, but it's really just that the default for the Page changed.

[PureWeen]

/backport to net7.0

[github-actions]

Started backporting to net7.0: https://github.com/dotnet/maui/actions/runs/5670519752

[github-actions]

@PureWeen backporting to net7.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Revert default for UseSafeAreaProperty to value from .NET 6 for iOS Fixes #12823
Applying: Update to ignore broken iOS test for now
Using index info to reconstruct a base tree...
M	src/Controls/tests/DeviceTests/Elements/TabbedPage/TabbedPageTests.cs
Falling back to patching base and 3-way merge...
Auto-merging src/Controls/tests/DeviceTests/Elements/TabbedPage/TabbedPageTests.cs
CONFLICT (content): Merge conflict in src/Controls/tests/DeviceTests/Elements/TabbedPage/TabbedPageTests.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 Update to ignore broken iOS test for now
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

[github-actions]

@PureWeen an error occurred while backporting to net7.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.