I am updating the package versions together with .net 9 and when migrating from Syncfusion.Maui.Popup 25.1.39 to 28.1.38 the Popup behavior changed.
Previous behavior:
Hide device navigation bar
Window?.AddFlags(WindowManagerFlags.Fullscreen);
Window?.AddFlags(WindowManagerFlags.LayoutNoLimits);
Window?.AddFlags(WindowManagerFlags.KeepScreenOn);
Window?.AddFlags(WindowManagerFlags.TranslucentNavigation);
WindowInsetsControllerCompat windowInsetsControllerCompat = new WindowInsetsControllerCompat(Window, Window.DecorView);
windowInsetsControllerCompat.Hide(WindowInsetsCompat.Type.SystemBars() | WindowInsetsCompat.Type.NavigationBars());
windowInsetsControllerCompat.SystemBarsBehavior = WindowInsetsControllerCompat.BehaviorShowTransientBarsBySwipe;
Window?.ClearFlags(WindowManagerFlags.ForceNotFullscreen);
For versions Build.VERSION.SdkInt >= BuildVersionCodes.R and version 25.1.39, when a Popup opens
popup.Show(true);
hidden SystemBars buttons are not displayed
New behavior:
For versions Build.VERSION.SdkInt >= BuildVersionCodes.R and version 28.1.38, when a Popup opens
popup.Show(true);
the hidden SystemBars buttons are displayed and a part of the popup footer is cut off to display the popup
Question:
Is there a configuration to display the Popup fullscreen without the bottom navigation bar being displayed for Build.VERSION.SdkInt >= BuildVersionCodes.R devices?
Hi Mateus Vinicius Miotto,
We sincerely apologize for any inconvenience this issue may have caused.
In release version 26.1.35, we implemented a feature to display the popup on top of the application, which required significant changes to the control architecture using WindowManager. Unfortunately, there have been unforeseen conflicts between WindowManager and WindowManagerFlags, leading to unexpected issues.
To address this, we need to reevaluate our current implementation with different WindowManagerFlags. As this process involves architectural revisions and thorough testing, we kindly ask for your patience while we work on it. We anticipate providing you with further details by January 21, 2025. We appreciate your patience until then.
Regards,
Anees Fathima.
Hi Mateus Vinicius Miotto,
Sorry for the inconvenience caused.
Currently we are working with priority on this reported scenario, and we are facing difficulties to find the root cause. So, we need some additional time to validate this scenario. We will provide further updates on or before January 24,2025
Regards,
Sowntharya J.
Hi Mateus Vinicius Miotto,
The use of the LayoutNoLimits WindowManagerFlag has caused issues with properly hiding the bottom navigation bar. As a workaround, we kindly recommend avoiding the use of the LayoutNoLimits WindowManagerFlag to ensure the popup displays in full screen without the bottom navigation bar.
Regards,
Sowntharya J.
Thank you for your attention and time dedicated to this situation.
By removing the WindowManagerFlags.LayoutNoLimits flag, when the popup is opened, the navigation bar continues to appear and the WindowManagerFlags.Fullscreen flag causes the footer to be displayed behind the navigation bar.
Using WindowManagerFlags.LayoutNoLimits:
Removing WindowManagerFlags.LayoutNoLimits:
So, using LayoutNoLimits, the popup doesn't stay the size of the screen, but it makes the footer a little higher and doesn't hide it, it also adds a bar in the top area. And by removing LayoutNoLimits , the popup remains full size, but the navigation bar is shown and hides the footer, to this tests i've using version 28.1.41
The closest expected behavior is not to use the LayoutNoLimits tag, but the navigation bar displayed means the footer is not shown.
If this behavior cannot be reached, please let me know.
I remain at your disposal if you need more information.
Regards
...
Hi Mateus Vinicius Miotto,
We sincerely apologize for the inconvenience caused. We understand your scenario and have noted that the previously shared workaround works in the Android Emulator but does not function as expected on real devices. We will further analyze the related WindowManagerFlags in the framework. We kindly request additional time to validate the reported scenario and appreciate your patience as we work on it. We anticipate providing you with further details by January 31, 2025. Thank you for your understanding.
Regards,
Sowntharya J.
Hi Mateus,
We would like to let you know that, we have logged a bug for the reported scenario, “ [Android] Popup Not Covering Bottom Navigation Bar When WindowManagerFlags.LayoutNoLimits Is Set ”, we will fix the issue and include the fix in our Upcoming nuget release, which is planned to roll out on February 25, 2025. We will appreciate your patience until then.
You can track the status of the issue in the feedback report below.
Feedback link: https://www.syncfusion.com/feedback/65065/android-popup-not-covering-bottom-navigation-bar-when-windowmanagerflags
Note: The provided feedback link is private, you need to login to view this feedback.
Regards,
Anees Fathima.
Hi Mateus,
We apologize for the inconvenience caused. We are unable to include the fix for this issue in this week's NuGet release. However, we will include the fix in our upcoming NuGet release, scheduled for rollout on March 4, 2025. We greatly appreciate your patience until then. In the meantime, We have attached a custom package with a fix for this issue. Please confirm whether the issue has been resolved on your side.
Note: Before installing the custom NuGet package, we recommend uninstall the Syncfusion packages from your application and clearing the NuGet cache.
How to install the MAUI custom NuGet in the Windows machine?
RootCause of the issue: In Popup, the overlay container is added directly to the window manager. As a result, setting flags for the DecorView in the sample no longer applies to the overlay container.
Regards,
Sowntharya J
Hi Mateus,
Please find the custom package below.
Regards,
Sowntharya J.
Hi Mateus,
We would like to let you know that Essential Studio Weekly NuGet packages (v28.2.9) has been published in nuget.org with the fix for the issue “[Android] Popup Not Covering Bottom Navigation Bar When WindowManagerFlags.LayoutNoLimits Is Set”. Please let us know if you have any concerns in this.
RootCause of the issue: In Popup, the overlay container is added directly to the window manager. As a result, setting flags for the DecorView in the sample no longer applies to the overlay container.
Regards,
Sowntharya J.
Hi Sowntharya.
I updated the packages to the latest version and now the behavior is as expected.
Thank you very much for your time.
Regards,
...
Hi Mateus,
We are glad to hear that the latest package has resolved the
issue. If you need any further assistance or encounter additional issues,
please feel free to reach out or open a new support ticket.
Regards,
Sowntharya J.