ui: statements page: Pass sort order as query parameters to persist sort state #29312
Labels
A-webui-routing
C-cleanup
Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
When reloading the Statements page or navigating back from the Statements details page, users lose their sort order since we are not tracking that anywhere. Instead, users should see the page in the state in which they last left it.
The text was updated successfully, but these errors were encountered: