Navigation back with anchors is broken

[aralroca]

Bug report

Describe the bug

When you enter directly on a page with an anchor and then you navigate to another page, everything is fine. But when you press to go back on the previous page, the navigation is broken.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

I created a reproducible example:

Code: https://codesandbox.io/s/nextjs-forked-660z5?file=/pages/index.tsx
Executable: https://660z5.sse.codesandbox.io/#example

1. Go to 'https://660z5.sse.codesandbox.io/#example' (with the #example hash)
2. Click on 'Navigate to page 2'
3. Press the browser button to navigate back
4. See error: The back button is not working well

Expected behavior

Should navigate back.

System information

• OS: macOS
• Browser: chrome
• Version of Next.js: 9.5.2
• Version of Node.js: 14.8.0

[Yogendra0Sharma]

@aralroca Working fine with Windows 10 + Chrome Version 84.0.4147.135 + ABove Link

[ijjk]

Hi, the above reproduction doesn't appear to be having any problems, we also have tests covering navigating with an anchor tag and back which are passing.

[littleninja]

Could it be related to #9833? (Might be worth noting that the linked issue is with macOS/iOS + Safari, the report here is macOS + Chrome.)

[aralroca]

A thousand apologies, because I thought I had reproduced it correctly and now I see that with the Codesandbox it doesn't happen to me either. In local it does happen to me, I am trying to reproduce it again from the sandbox. While I close the issue, I'll open it again after creating a reproducible example.

[aralroca]

Meanwhile, I share a video here about what is happening to me:

video.mov.zip

Some details:

• I'm using a custom server
• I'm using the function getServerStaticProps on the page of the hash
• I'm using Preact
• I'm using next-translate with the custom server approach (middleware)

I'll try to do a reproducible example

[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.