using cookies for that is not a good pratice. This should be handled by the client. So handle the state on the client. For example using a useState. This state will also persists when the browser cache is enabled

so youre saying useState will not reset its state when navigating?

how?

yes, it saved inside the browser cache and is preserved

what about when the user full page reloads the page?

then the state resets

can you share the link to the screenshot? thanks! @B33fb0n3

this is the link: https://nextjs.org/docs/14/app/building-your-application/caching#router-cache

@B33fb0n3 the docs are misleading,

this issue explains https://github.com/vercel/next.js/issues/58699

use a query param

easy life, built in state controller by the browser

depending on the use case it's useful if you need to copy the link to someone when ther is an issue

it works clearly fine as you can see here: https://codesandbox.io/p/devbox/xn54j6

This is a reproduction of the solution perfectly matching to your use case.

How to test?
1. Scroll down the sidebar on the left
2. Click the red Link or the sections
3. See Results -> Even if you switch the route, the scrolling position and the expanded sections (the Colors above the red link) persists

@Bakharwal dog solved?

You ssr a sidebar?

Oh shit, not a slide out sidebar that's has like form stuff on it

A literal sidebar nav 🤣

@B33fb0n3 it was solved by not having 2 layout.tsx

not sure why, it stopped re-rendering when I put the sidebar in the main layout

so I didn't lose the scroll position on navigation

So you now leveraging the browser cache to persists the states and you now using client side states that are handled by the client, right?

it doesnt even re-render, when i turn on the react dev chrome extension

the scroll bar is not part of the state

the only reason it doesn't reset - means it did not unmount

would you mind taking a look at my new problem? lol

Yea, the scroll bar position is only saved inside the browser cache. And due no rerender of the layout all states persists as well

I'll help you with this one, but I don't think I'll be able to help you with future issues. It's a bit too much work to write inside your threads.