Prevent NavigationPage & TabbedPage from inheriting parents BindingContext

[brianlagunas]

Description of Change

By default, elements in a XF app will always inheit their parent's BindingContext. This becomes an issue when using a FlyoutPage and a TabbedPage and then using a NavigationPage as a child. The NavigationPage will inherit the parents BindingContext which would then invoke the Prism navigation interfaces when they shouldn't be invoked.

We fix this by preventing the NavigationPage and TabbedPage from inheriting their parent's BindingContext.

Bugs Fixed

• [Bug] Flyout page INavigationAware events incorect triggering #2587

API Changes

None

Behavioral Changes

The NavigationPage and TabbedPage types will no longer inherit their Parent's BindingContext. If you would like for these types to have a iffeent BindingContext, you will have to register a ViewModel with the Prism NavigatinService.

PR Checklist

• Has tests (if omitted, state reason in description)
• Rebased on top of master at time of PR
• Changes adhere to coding standard

[dansiegel]

thank you for publishing a PR with the code I sent you 😆

[brianlagunas]

So that's your definition of paired programming... okay... I'll remember that