Is your feature request related to a problem? Please describe.
There are lots of situations where you don't want to push/pop the entire full page on screen. It would be useful to be able to perform most navigation actions but target the most "visible" or "deepest" navigation page. E.g. if you could push a page to the currently visible tabview on top of a page that is already there (So that if you pressed the Android back button, it would go back to the original page that was in the tab view).
Describe the solution you'd like
I'd like to be able to easily decide whether to push a page over a flyoutpage/tabbedpage or instead push a page into a NavigationPage stack. It should be clear and unambiguous where the page should go. Ideally, this should work with all existing methods and URI navigation. Maybe it should be a navigation parameter? TargetNavigationPage maybe?
Is your feature request related to a problem? Please describe. There are lots of situations where you don't want to push/pop the entire full page on screen. It would be useful to be able to perform most navigation actions but target the most "visible" or "deepest" navigation page. E.g. if you could push a page to the currently visible tabview on top of a page that is already there (So that if you pressed the Android back button, it would go back to the original page that was in the tab view).
Describe the solution you'd like I'd like to be able to easily decide whether to push a page over a flyoutpage/tabbedpage or instead push a page into a NavigationPage stack. It should be clear and unambiguous where the page should go. Ideally, this should work with all existing methods and URI navigation. Maybe it should be a navigation parameter?
TargetNavigationPagemaybe?Describe alternatives you've considered N/A
Proposed APIs N/A
Additional context N/A