Skip to content

[Android, iOS] ContentPage.SafeAreaEdges = Default applies safe area like a container instead of being edge-to-edge (None) #34872

@TamilarasanSF4853

Description

@TamilarasanSF4853

Description

When ContentPage.SafeAreaEdges is explicitly set to Default, the ContentPage applies container-like safe area padding. This contradicts the documented(https://learn.microsoft.com/en-us/dotnet/maui/user-interface/safe-area?view=net-maui-10.0#safeareaedges-enum) and intended behaviour, where Default on a ContentPage should resolve to None (edge-to-edge).

Screen.Recording.2026-04-08.at.1.05.59.PM.mov

Steps to Reproduce

  1. Run the attached sample: SafeareaIssue.zip
  2. Click the Default button and notice the changes.

Link to public reproduction project repository

No response

Version with bug

10.0.51

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

Unknown/Other

Affected platforms

Android, iOS

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-safeareaIssues/PRs that have to do with the SafeArea functionalitypartner/syncfusionIssues / PR's with Syncfusion collaborationplatform/androidplatform/ioss/triagedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions