[NEXT-614] Navigation changing just `searchParams` doesn't trigger `loading.tsx`

[jankaifer]

    When navigating from foo?page=1 to foo?page=2, the foo/loading.js script is not triggered. Is this normal behavior or a bug?

Originally posted by @wh5938316 in #41745 (comment)

_NEXT-614

[wh5938316]

Any updates on this?
It seems that changes to searchParams in next.js 13 may not be considered as page changes.
When a Link is clicked and only the searchParams are changed, the page does not scroll to the top despite the scroll props being set to true.

https://app-dir.vercel.app/snippets/search-params

I'm wondering if this behavior is intentional or a mistake.

[hoqua]

Any updates on this?

I guess this feature is must have to consider using the NextJS app dir in production

[timneutkens]

On next@canary a fix for the cache key with searchParams was landed: #47312

However changing searchParams as-is will cause it to match up keys higher up so in some cases you'll have to add a <Suspense> boundary that has a key where you want to show a boundary if it's changing in a meaningful way.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.