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
On a page with a table that has multiple pages (community, binders etc) you cannot return to your exact position in the table, let's say page 20, after you have opened a link (someone's collection or a binder). To return you either have to navigate back via the browser's back button or click on the navigation menu but you will always return to page 1 of the table.
Desired Functionality
Perhaps a button to return to where you just were (that exact page in the table)? Back button, close button, something like that? Or open the page as some kind of overlay/new layer like the individual cards when you browse a collection and look at a specific card - that can be closed via the x button. Might be difficult, but would be more user friendly.
The text was updated successfully, but these errors were encountered:
This can be solved using query parameters. Definitely makes sense to for us to add this.
GuthrieW
changed the title
Feature Request (Submitted by 3723)
Feature Request (Submitted by 3723) - Add page number to query params for pages with tables
Dec 29, 2024
Description
On a page with a table that has multiple pages (community, binders etc) you cannot return to your exact position in the table, let's say page 20, after you have opened a link (someone's collection or a binder). To return you either have to navigate back via the browser's back button or click on the navigation menu but you will always return to page 1 of the table.
Desired Functionality
Perhaps a button to return to where you just were (that exact page in the table)? Back button, close button, something like that? Or open the page as some kind of overlay/new layer like the individual cards when you browse a collection and look at a specific card - that can be closed via the x button. Might be difficult, but would be more user friendly.
The text was updated successfully, but these errors were encountered: