-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safe Area not working for iOS #19720
Comments
We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process. |
I'm encountering the same problem on iOS. |
Same here, experience this in 8.10 |
Same issue here on 8.0.14 |
1 similar comment
Same issue here on 8.0.14 |
Same issue on 8.0.20 |
same problem here |
same problem here. |
same problem |
Same problem |
Description
I have a problem with the safe area for iOS. I used the sample project to recreate the problem
When I push the "click" me button, a modalPage with be pushed with Navigation.PushModalAsync.
If I use ios:Page.UseSafeArea="False", it still has a safeArea and look like this:
However, if I set IgnoreSafeArea="True" on the stacklayout instead, it will work as I intend:
Steps to Reproduce
xmlns:ios="clr-namespace:Microsoft.Maui.Controls.PlatformConfiguration.iOSSpecific;assembly=Microsoft.Maui.Controls"
ios:Page.UseSafeArea="False"
to MainPage.Xaml.
Expected outcome: There is no safe area
actual outcome: Safe area is still there
Link to public reproduction project repository
No response
Version with bug
8.0.3
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
My workaround is to use IgnoreSafeArea="True", however it seems inconvenient to do as it has to be done for each grid/stacklayouts, also sometimes for the inner ones.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: