Scroll is not restored after navigating with back button after swipe to top

[l-you]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Current https://nextjs.org version is 13.4.17-canary.2

Which example does this report relate to?

https://nextjs.org

What browser are you using? (if relevant)

IOS Safari 16.6

Describe the Bug

When using the browser's provided back button following a quick upward swipe, the scroll position resets for the previous page.
Please note that this issue only occurs in iOS Safari and cannot be replicated in IOS Chrome.

Expected Behavior

Scroll position should be restored.

To Reproduce

1. Visit https://nextjs.org.
2. Scroll down to a sufficiently distant link.
3. Click on that link.
4. The navigation bar has disappeared. To return, swipe up quickly and then click the back navigation. (Usually, the combination of those actions performed quickly)
5. The scroll position is not restored.

Please look at the following video.

6d05fcf7-318f-4dc3-85e4-6792e14fd6ba.mp4

Update:
Seems like a general bug for every website for both manual and auto scroll restoration only on IOS Safari.
Here is screen recording of reproduction on google.com website.

RPReplay_Final1692286299.2-2.mp4

[yoonjaepark]

I have the same problem.
In the local environment, scroll restore is enabled. If you build it and go up to the development environment, the scroll is only IOS. Ios Chrome also scrolls back up to the top.
Next13.5.6 is in use.
First, I am implementing it by switching only to history.scrollRestoration.

[l-you]

I have the same problem. In the local environment, scroll restore is enabled. If you build it and go up to the development environment, the scroll is only IOS. Ios Chrome also scrolls back up to the top. Next13.5.6 is in use. First, I am implementing it by switching only to history.scrollRestoration.

I was forced to make my implementation of scroll restoration.
I've made it as a library. Feel free to take a look.
But in newer versions of NextJs sometimes it works incorrectly. I would be glad if someone suggested a better solution.

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[l-you]

Why?