Full screen Popup on Rounded Edge Device

[Daniel Kelly]

When using a SfPopup in full screen mode on devices with Rounded Edges (aka Galaxy A16), the footer contents are hidden / not displayed properly and behind the rounded edges.

Are there any workarounds that can be applied? No SafeEdges available in Popup.

Daniel.

Attachment: Sfpopup1_e8cac262.jpg

[Muthukumar Madasamy]

Hi Daniel,

Thank you for reaching out to us.

Could you please confirm whether you have applied SafeAreaEdges for your ContentPage? This property ensures that the UI respects the device’s safe area and avoids overlapping with rounded corners or notches.

Additionally, it would be very helpful if you could share a simple sample that replicates the issue. This will allow us to analyze the scenario in detail and provide you with the most accurate solution or workaround.

Looking forward to your confirmation and sample.

Best Regards,

Muthu Kumar M

[Daniel Kelly]

Hi,

It could be the way Im using the PopUp page as it is self contained and not within a Content Page.  So there is no SafeAreaEdges option to set inside the Popup.  The reason for this is to create reusable popups like we used to with Xamarin Forms.

I have attached a minimal sample app showing the issue.

Thanks,

Daniel

Attachment: TestingPopUp_cd073c67.zip

[Muthukumar Madasamy]

Hi Daniel,

Thank you for sharing the sample and additional details. We have analyzed the scenario and confirmed that the issue occurs because the popup is rendered in full-screen mode without respecting the device’s safe area when immersive flags are applied.

To resolve this, we recommend updating your MainActivity to ensure the content (including popups) respects Android safe areas. Below is the modified implementation:

Updated MainActivity:

private void SetFullScreen() {

    if (this.Window == null) return;

    WindowCompat.SetDecorFitsSystemWindows(this.Window, false);

    // Remove immersive full-screen flags that cause content to render under bars

    this.Window?.ClearFlags(WindowManagerFlags.Fullscreen);

    this.Window?.ClearFlags(WindowManagerFlags.TranslucentNavigation);

    // this.Window?.ClearFlags(WindowManagerFlags.LayoutNoLimits); // keep default

    // Keep screen on if desired (optional)

    this.Window?.AddFlags(WindowManagerFlags.KeepScreenOn);

    // Show system bars to compute proper insets for layout

    WindowInsetsControllerCompat windowInsetsController = new WindowInsetsControllerCompat(this.Window, this.Window.DecorView);

    windowInsetsController.Hide(WindowInsetsCompat.Type.SystemBars());

    windowInsetsController.Hide(WindowInsetsCompat.Type.StatusBars());

    windowInsetsController.Hide(WindowInsetsCompat.Type.NavigationBars());

    windowInsetsController.SystemBarsBehavior = WindowInsetsControllerCompat.BehaviorShowTransientBarsBySwipe;

}

Sample and Output:

We have attached a working sample and an output screenshot demonstrating that the footer content is now properly displayed within the safe area on rounded-edge devices.

Please try this approach in your application and let us know if it resolves the issue. If you need further assistance or have additional requirements, feel free to reach out we’re happy to help.

Best Regards,

Muthu Kumar Madasamy.

Attachment: Sample_and_output_7e7eb29e.zip

[Daniel Kelly]

Hi,

Sorry, I have deployed to my Samsung Galaxy A16 and the same issue occurs.

I cleaned and rebuilt the project and uninstalled from device before re-deploying to ensure no remnants were left.

Thanks,

Daniel.

[Muthukumar Madasamy]

Hi Daniel,

 

We have analyzed the scenario further and observed that the reported issue seems to occur only in .NET MAUI 10. We are currently validating the behavior and checking for any changes related to window management and safe area handling in .NET 10 compared to .NET 9.

 

We need two more working days to complete our investigation. We will update you with detailed findings and the next steps on or before December 05, 2025.

 

We appreciate your patience and understanding in the meantime.

 

Best Regards,
Muthu Kumar Madasamy

[Muthukumar Madasamy]

Hi Daniel,

We have checked your query at our end, and we are able to replicate that issue at our end when using WindowManager fullscreen. We have considered this as a bug and logged a bug report regarding this in our feedback portal. We will fix the reported issue and include the changes in our upcoming weekly patch release, which is expected to be rolled out on Dec 23, 2025. We will let you know once released, and we appreciate your patience until then. You can also track the status of the bug using the feedback link below.

Feedback Link: 71672

Disclaimer: Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization.

Best Regards,

Muthu Kumar Madasamy.

[Santhosh Natarajan]

Hi Daniel,

We regret to inform you that we are unable to address this issue in the current weekly release. However, we are actively working on a fix and have scheduled the resolution for our upcoming weekly patch release, which is expected to be rolled out on Dec 30, 2025. We will let you know once released, and we appreciate your patience until then. 

Best Regards,

Santhosh Natarajan

[Muthukumar Madasamy]

Hi Daniel,

We are glad to inform you that the reported issue regarding the “SfPopup renders outside visible bounds in Android when using WindowManager fullscreen flags” has been resolved. This fix has been incorporated into our latest weekly NuGet release. To benefit from this fix, we recommend updating your SfListView package to version 32.1.21.

NuGet Gallery | Syncfusion.Maui.Popup 32.1.21

Root Cause of the issue:

In .NET 9, hiding the status bar only hides the text (time, battery), but the bar itself remains, so decorViewFrame.Top returns the bar’s height. In .NET 10, hiding the status bar behaves similarly visually, but internally the system reports decorViewFrame.Top = 0, as if the bar doesn’t exist. This difference causes layout issues.

We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you require any further assistance.

Best Regards,

Muthu Kumar Madasamy.