-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
NavigationPage shows title bar before navigating #21134
Comments
This is on some level by design. In XF every single page had its own toolbar so what's getting pushed is the entire screen with or without a toolbar. in MAUI the toolbar is part of the chrome, so what we're seeing here is the toolbar hiding/showing as a new page is pushed onto the stack. In XF you'd get this animation when you pushed where the entire page (including toolbar) would swipe onto the screen, which isn't really desirable. Shell still does this We could probably look at improving the animation or timing of the navbar though so it's less abrasive. |
Verified on 17.10.0 Preview 2.0, can repro on android platform with sample project. |
I just added a project that reproduce this issue above. Here it is again: https://github.com/leo-mck/MauiNavigationPageTestApp |
Description
I am migrating a Xamarin.Forms app to MAUI and in some cases I have a ContentPage with
NavigationPage.HasNavigationBar="False"
that navigates to a ContentPage withNavigationPage.HasNavigationBar="True"
. On XF, this works as expected but on MAUI (android) the NavigationPage title bar push the previous page content down before navigating. This is not using shell.navpage_xf.mp4
navpage_maui.mp4
Here is a frame showing the problem. We are seeing the first page but with the second page title bar.
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
8.0.7 SR2
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: