Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I have a cross platform app that works correctly on Android and iOS but has a display problem on UWP.
The app has a CarouselPage as the main window inside a NavigationPage.
The CarouselPage has NavigationPage.HasNavigationBar=false to hide the navigation bar.
A button on one of the carousel content pages calls PushAsync on the NavigationPage to display a sub-page.
After the back button is pressed, the carousel's current page is restored but the page is missing the bottom 48 pixels.
This is exactly the height of the hidden navigation bar.
Any subsequent operation that causes a layout of the carousel page restores the missing 48 pixels; e.g. next/previous page.
As a workaround, I can attach a handler to the carousel page Appearing event to call ForceLayout on the top level NavigationPage.
I think the Xamarin team would tell you :NavigationPage.HasNavigationBar will close the Navigation page navigation bar which your using,(In your case sounds like your open 2 page in navigation page, push and pop, if you close it from one child page, it will of course affect with other), But I can't too much understand how it worse, I hope you could take a time and do some sample, let the team understand the worst part.
Are you still experiencing this with the latest stable/prerelease versions, and if so, can you upload a reproduction to provide a better idea of what you mean?
Because we have not received a reply to our request for more information we are
closing this issue. If you are still encountering this issue, please reopen the
ticket with the requested information. Thanks!