-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
persist nav state #209
persist nav state #209
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be working as you describe and after just navigating around a bit, it definitely feels better to have the sidebar not lose its place. One thing I noticed was I found the search filter persisting after I hit the back button to be a bit surprising. I don't even know why this stood out to me - I just expected the filter to clear.
To me this isn't a blocker and the benefits of these updates outweigh this - mostly just sharing because I'm curious if someone knows about some design/UX convention where I may have subliminally picked this up 😆 Looks good, though!
Thanks for testing!
That's interesting, thanks. I debated doing it both ways and this seemed convenient for navigating within a group of related items ('button' was the filter term I used a lot.) Let's raise it as a question/tension in the next tactical. |
One idea: could persist trailing debounced changes (wait time ~2s) to the filter as query string changes and push them onto the browser history stack. For example:
|
<3 |
created follow-up issue here: #213 |
Description
Persist side nav bar scroll position and filter state using
Window.sessionStorage
, which should be per-tab.Issue addressed
fixes #182
Before/after screenshots
Steps to test
Experiment with navigation through the design system and see how it feels
(optional) Implementation notes
At a high level, how did you implement this?
mounted
Does this introduce any tech-debt items?
Reviewer guidance
Comments