Reset scroll position after navigation. Fixes #10482

[SteveSandersonMS]

This only affects link clicks and programmatic navigation.

For back/forwards, browsers already apply their own native scroll position restoration behavior, which varies between browsers, so we leave that alone.

[javiercn]

This is kind of confusing. I would have simply used methods for this.

[javiercn]

Great change!

Straightforward and with E2E, nice!

[kaveh6202]

I think there is a problem with this approach , you see, I have a collapse component in my page and it is kind of in the bottom of the page . when i toggle a tab within my component , the normal behavior for page in this situation is not to scroll and stay put since i have inner page link ( starts with # ) in href attribute of my "a" tag.

[smirceamihai]

Agree with @kaveh6202
Please consider:

• Turning this into an optional (parameter) feature for the NavigateTo method
• Disabling the scroll reset if the navigation goes to the same LocalPath (only query params change)

For us the workaround was overriding the default behavior with an interop method:

async function navigateToState (url) { history.replaceState(null, null, url); await DotNet.invokeMethodAsync( 'Microsoft.AspNetCore.Components.WebAssembly', 'NotifyLocationChanged', url, false // IsNavigationIntercepted ); }

[ghost]

Hi @smirceamihai. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

[christallire]

Agree with @kaveh6202 Please consider:

• Turning this into an optional (parameter) feature for the NavigateTo method
• Disabling the scroll reset if the navigation goes to the same LocalPath (only query params change)

For us the workaround was overriding the default behavior with an interop method:

async function navigateToState (url) { history.replaceState(null, null, url); await DotNet.invokeMethodAsync( 'Microsoft.AspNetCore.Components.WebAssembly', 'NotifyLocationChanged', url, false // IsNavigationIntercepted ); }

for anyone who stumbled this on .NET 7
there's some internal changes at the API. need to add history argument after the url like this:

await DotNet.invokeMethodAsync( 'Microsoft.AspNetCore.Components.WebAssembly', 'NotifyLocationChanged', url, '', false);

[ghost]

Hi @christallire. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.