Blazor NavigationManager.NavigateTo always scrolls page to the top.

[groogiam]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

It appears the navigation manger in .NET 6 always scrolls the page to the top even if NavigateTo call is just updating the query string.

Expected Behavior

Navigations that do not change the page should not reset the viewport position.

Steps To Reproduce

Will post a repro shortly.

Exceptions (if any)

No response

.NET Version

6.0.102

Anything else?

No response

[groogiam]

Repro

https://github.com/groogiam/AspNetCore40190Repro

[rogihee]

.NET6 has a new API to manipulate the query string NavigationManager.GetUriWithQueryParameter, see the docs here https://docs.microsoft.com/en-us/aspnet/core/blazor/fundamentals/routing?view=aspnetcore-6.0#query-strings

Did you try that?

[groogiam]

@rogihee Thanks for the tip. I have tried this. That api does not actually navigate to anything it just gets a new value for the querystring. This does not really solve the issue as I still have to navigate to that uri to update the browser url and the NavigateTo call is what is scrolling the viewport needlessly.

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.

[lukblazewicz]

Just to bump up - this behaviour affects our application as well (quite significantly). Is there any workaround for that until the issue gets resolved?

[groogiam]

@lukblazewicz I have had some success using JS interop to capture the current page scroll position and and then trying to reset the position after the update query string operation completes. I had to add some random Task.Delay statements in my C# code to get things to work and the user experience is still pretty bad as the page jumps up and then back down but at least your users don't have to scroll manually back to where they were. Hopefully this helps.

[groogiam]

@mkArtakMSFT I'm not sure why this is tagged as an enhancement, I'm fairly certain this it is a regression from Blazor on .NET 5. The issue did not manifest until I upgraded from .NET 5 to .NET 6. This regression really impacts user experience of this product.

[lukblazewicz]

@groogiam Thanks for the tip, we will have to consider it if there is little hope to get this bug fixed soon.
@mkArtakMSFT Is there any chance this issue gets promoted to be fixed in the upcoming releases?

[dp-sgr]

@groogiam Sounds like #36605

Look at the Workaround from @smirceamihai:

#12423 (comment)