Consistent scroll behavior between Router.push and Link

[oyeanuj]

Feature request

Is your feature request related to a problem? Please describe.

I noticed that when using Link, you can specify option to prevent scrolling to top but the same option seems missing when using Router.push: https://nextjs.org/docs/api-reference/next/router#routerpush

(Additionally, when using browser back buttons, the same scroll behavior happens)

Describe the solution you'd like

A scroll option in the router.push method to specify whether page should be scrolled to the top or not. This would make the behavior in the method consistent as they are supposed to be parallel methods.

Additional context

It seems like here in the code, there needs to be a check for scroll:

next.js/packages/next/next-server/lib/router/router.ts

Lines 738 to 740 in 23db226

	if (hash === '') {
	window.scrollTo(0, 0)
	return

---

Finally, thank you for all the work that y'all do, and thank you for creating this wonderful library!

[nfantone]

Sharing a possible workaround here as well for anyone stumbling upon this issue.

[Timer]

Closing as duplicate of #3249

[finnss]

I disagree that this is a duplicate. #3249 is entirely focused on stopping the scroll to the top. I am currently having the issue that router.push jumps my page to the top, which I'd like to avoid in my use-case.

I assume the behaviour was changed to always reset(0, 0) in next@canary.
I (and probably others) sometimes want to keep the scroll position after a push, and some sort of scroll option like we have with the <Link> component seems like the real solution @Timer.

If I'm mistaken and this already exists as an option, my bad! I couldn't find anything in the documentation or any existing issues.

EDIT: Nevermind! scroll is indeed a valid option for router.push: https://github.com/vercel/next.js/blob/canary/packages/next/next-server/lib/router/router.ts#L767
Keeping this comment in case anyone else stumbles upon this issue. A note about this in the documentation might be a good idea:) Thanks again for all the hard work you do!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.