You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, some parts of the UI state are synchronized with the url via query parameters (like currently open panels etc.). Similarly, it would be great if the criteria the user inputs when performing a search could be synchronized with the query.
This way, by sharing the current url with another user, that second user would have the search criteria pre-filled and would see the same results as the first user.
This could apply to the /search page as well as to the filter boxes while browsing.
The text was updated successfully, but these errors were encountered:
In Search, this could also reflect whether it was submitted and auto-submit on reload.
If you ask me, it could auto-submit by default, because the reason a user might want to share a search input configuration is to show another user the results first and foremost (and the input params as a byproduct).
What would be the reason/use case for loading the search criteria without triggering the submit?
The query could actually be only set once the user triggers the search, this way it would make sense also in the other direction.
But I do not have a strong opinion about this, in the end I'm up for whatever is easier to implement I guess 😄
If I select something in the form without submitting and then reload the page (for whatever reason), it's weird that it would auto-submit. But let's see in implementation what makes sense, it's minor thing anyway.
Currently, some parts of the UI state are synchronized with the url via query parameters (like currently open panels etc.). Similarly, it would be great if the criteria the user inputs when performing a search could be synchronized with the query.
This way, by sharing the current url with another user, that second user would have the search criteria pre-filled and would see the same results as the first user.
This could apply to the
/search
page as well as to the filter boxes while browsing.The text was updated successfully, but these errors were encountered: