-
Notifications
You must be signed in to change notification settings - Fork 17
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
Back button behaviour often loses state in search #50
Comments
From @ValWood.
|
@ValWood If this is a common pattern, you can also "bookmark" your search. By clicking on that link, you will go to a bookmarked/pinned version of your current search, so you can always get back to the same spot. |
Its pretty much every search I do, so I'd need to bookmark everything.... Can you make the default list longer (say 50). This would help a little. At present I need to reset the list length every single time I look at anything over the 10th entry. |
When clicking the back button after leaving a search page, the search is lost.
This could be fixed by: adding the bookmark of the current search to the url on every action (if it doesn't try to forward.). Otherwise, a fragment could be added to the URL which is probed for when landing, and resolved when found (standard two-pass, like we have now).
This issue can be moderated by making sure that users know that they can open external/jump links in new tabs, either with click or client settings.
The text was updated successfully, but these errors were encountered: