When using a querystring with Blazor apps the the default NavItem is not selected.

[PaulSinnema]

Describe the bug

This happens in a client side application.
When you use a NavItem in your MainLayout like in the default generated application and you call the application with a querystring f.i. https://localhost:123456/?CourseId=123456 then the first NavItem that normally becomes the selected one is displayed as not selected.

To Reproduce

• Generate a new Blazor Client side application
• Run the application
• In the addressbar of the browser put a querystring behind the url f.i. https://localhost:44381/?CourseId=13333 and press enter
• Notice how the 'Home' menu no longer is selected.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[PaulSinnema]

We worked around this. When we receive the querystring we take the parameters we need and store it in the session objects. After that we redirect to the same page without the querystring. You do get a second load of the page but for a SPA that is not very disturbing and only the first time you reach the page.

[heidarj]

Hey I've taken a look at this and I suspect https://localhost:123456/?CourseId=123456 is not matching because the 'Home' NavLink for new Blazor projects has Match="NavLinkMatch.All" set. Maybe the documentation could be updated to clarify how the Match attribute works with querystrings?

[uabarahona]

This was a monster!

@captainsafia @pranavkm should this be closed already?

[PaulSinnema]

This a very ugly bug. Don't close it but solve it please.