Pull Request Overview

This pull request implements a comprehensive safe area handling system for Android platform in .NET MAUI, introducing per-edge safe area control and keyboard awareness. The implementation adds a centralized SafeAreaHandler class to manage safe area insets consistently across different view types while optimizing performance through caching and hierarchy traversal optimizations.

• Introduces unified safe area handling with SafeAreaHandler class for consistent behavior across ContentViewGroup and LayoutViewGroup
• Adds per-edge safe area control through new SafeAreaPadding record and WindowInsetsExtensions
• Integrates keyboard-aware layout adjustments that respond to IME visibility changes

Reviewed Changes

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

These are the tests to validate the changes, right?
#30908

Could we expand it to support more edge cases? I would include more tests like:

• SafeAreaBorderOrientationPortraitToLandscape - Tests orientation change from portrait to landscape, verifying that the safe area adapts, the border dimensions change, and insets adjust on notched devices.
• SafeAreaBorderOrientationLandscapeToPortrait - Tests orientation change from landscape to portrait, ensuring the safe area reverts correctly and border dimensions differ between orientations.
• SafeAreaBorderMultipleOrientationChanges - Tests multiple sequential orientation changes (portrait to landscape and back), verifying border visibility, positioning consistency within the same orientation (with tolerance), and overall stability.
• SafeAreaBorderSoftInputBehavior - Tests soft input (keyboard) behavior with bottom edge set to SoftInput, checking that the border shrinks when the keyboard appears and returns to original size after dismissal.
• SafeAreaBorderSoftInputWithOrientationChange - Tests soft input with orientation change (portrait to landscape) while keyboard is visible, ensuring the border maintains visibility and dimensions differ between orientations.

I still need to review this a little bit deeper but I do still wonder about @albyrock87 's comment here

#31022 (comment)

I wonder about the approach here with storing the safea area into separate handlers and then modifying the arrange pass.

In theory could we just have a global handler that sets the padding on the view?

Basically what I've done to fix the safearea on various views for edge to edge is just set the padding inside the windowinset listener

could we take the same approach here? Like, we just have a window listener applied to ContentViewGroup and LayoutViewGroup and then inside the "ApplyWindowLIstener" it extracts the safeareas and sets the padding on the views.

If the padding is set on the views than the measure and arrange passes will just work. The main reason we don't do this approach on iOS (AFAIK) is that iOS doesn't really have a concept of "padding" you can set on views, you always just fake the padding inside LayoutSubviews.