Is your feature request related to a problem? Please describe.
After navigating a few pages of results on the audio recordings list view, and then navigating to an item, after clicking back in the browser, the table state is reset (page is back at 0)
Describe the solution you'd like
Navigational state should be preserved when manipulating tables.
[ ] Ensure the changes affect all pages with tables (make the change in the pagination directive I think?)
[ ] Set the current paging properties as query string parameters (sort by, and page), and register the changes as page history state changes
[ ] Catalogue our usages of the table component and make sure these changes don't introduce undesired behaviors
(e.g. in places where a table has been misused, these navigational changes could affect page flow).
Is your feature request related to a problem? Please describe.
After navigating a few pages of results on the audio recordings list view, and then navigating to an item, after clicking back in the browser, the table state is reset (page is back at 0)
Describe the solution you'd like
Navigational state should be preserved when manipulating tables.
Describe alternatives you've considered
N/A
Additional context