Replies: 1 comment 3 replies
-
Saved state on web is supported by local storage and session storage concepts. They are the same API but local storage exists on disk essentially until the user clears it while session storage is tied to the current tab and will be cleared when it is closed. You can read more about it here: https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API If you run Scroll state is handled by the browser -- I'm not really sure I have much control over that. That said, you can use fragments (using the '#' character) as a way to control scrolling. For example, something like https://bitspittle.dev/blog/2022/kotlin-site#conclusion |
Beta Was this translation helpful? Give feedback.
-
Hi,
I do not see clearly in the docs any management by the router of state restoral, scroll position restoral. Is this because state is intended to be managed at the app level, via the URL, or some other way when navigating back through routes previously visited?
For example, the playground app, if I enter a user name then go to another tab, and return, the user name is lost. Obviously it isn't intending to handle that in this codebase, but probably should. How would it?
Beta Was this translation helpful? Give feedback.
All reactions