Nextjs docs claim state is not lost between navigation? (Client side cache)

[gmoniava]

In the Nextjs App router docs about Client side cache it says:

• No full-page reload between navigations and React state and browser state is preserved.

I can't reproduce it. See here.

• Click "First Link" button, increase counter
• Click "Second Link" button
• Click "Back", to go back where the "First Link" took you
• See the counter state is 0 again

Why was the counter reset? According to above quote wasn't the counter supposed to retain value?

---

Ps there is similar quote from another section of docs which seems to imply same thing:

By default, the browser performs a hard navigation between pages. This means the browser reloads the page and resets React state such as useState hooks in your app and browser state such as the user's scroll position or focused element. However, in Next.js, the App Router uses soft navigation. This means React only renders the segments that have changed while preserving React and browser state, and there is no full page reload.

[tehandyb]

Adding to this, on my local development environment when using the PAGE based router it DOES preserve state between pages. But when deployed to a production-like environment it doesn't preserve state, and does full mounting of components with new state. Weird behavior