You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
To Reproduce
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
Expected behavior
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
Screenshots
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
OS version
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
.NET version
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
WPF-UI NuGet version
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
Additional context
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
The text was updated successfully, but these errors were encountered:
Describe the bug
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
To Reproduce
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
Expected behavior
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
Screenshots
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
OS version
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
.NET version
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
WPF-UI NuGet version
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
Additional context
Actually, when I'm calling NavigationView, the SelectedItem can't be accessed directly since it's protected. And when I try to use typeof with Navigate, it just shows the object as undefined. It feels really inconvenient, and the design kind of forces you to work with the structure they provided.
The text was updated successfully, but these errors were encountered: