Incorrect information in the docs about client side router cache?

[gmoniava]

In the caching guide it says:

When a user navigates between routes, Next.js caches the visited route segments and prefetches the routes the user is likely to navigate to. This results in instant back/forward navigation, no full-page reload between navigations, and preservation of React state and browser state.

But I am pretty sure if I visit a client component then navigate to a different URL, current component gets unmounted, hence state won't be preserved. What am I missing?

Here is also demo:

• 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

@icyJoseph

[icyJoseph]

Uh that's a loaded line if I ever seen one ~

Yes, as of today, state at app/foo/bar/page.js will get lost when you go to app/foo/bazz/page.js - however, if you have state at the root layout, through an imported Client Component, or even at app/foo/layout.js - that state will be preserved.

Formally speaking it should be shared layouts - I think - I don't remember right now if Parallel routes have some game here, they can also have layouts too, so I guess, shared layouts still applies ~

• https://stackblitz.com/edit/stackblitz-starters-cx9xkmdj?description=The%20React%20framework%20for%20production&file=app%2Flayout.tsx&title=Next.js%20Starter

And I say of today because the React Activity, challenges that :) https://react.dev/reference/react/Activity#noun-labs-1201738-(2)

[gmoniava]

I see, thanks. So will the docs be updated? Because confusing sections like this can be quite demotivating for readers.