We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Use the Playground.Uwp-App and add another Frame to ChildView.xaml before the "NestedFrame"-Frame
In the Playground.Uwp-App try to open the SplitView-Page
The name in the MvxRegionPresentationAttribute should not be ignored so just Views with the correct name are used.
The SplitView Demo opens and shows pane and content.
Always the new Frame is used for the SecondChildView instead of the NestedFrame which should be used.
The app crashed with an MvxException saying "Failed to find a SplitView in the visual tree of SplitMasterView"
Version: 5.5
Platform:
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Steps to reproduce 📜
Use the Playground.Uwp-App and add another Frame to ChildView.xaml before the "NestedFrame"-Frame
In the Playground.Uwp-App try to open the SplitView-Page
Expected behavior 🤔
The name in the MvxRegionPresentationAttribute should not be ignored so just Views with the correct name are used.
The SplitView Demo opens and shows pane and content.
Actual behavior 🐛
Always the new Frame is used for the SecondChildView instead of the NestedFrame which should be used.
The app crashed with an MvxException saying "Failed to find a SplitView in the visual tree of SplitMasterView"
Configuration 🔧
Version: 5.5
Platform:
The text was updated successfully, but these errors were encountered: