Open jameskoster opened 9 months ago
bgardner
commented
3 months ago Huge fan of this, particularly for Layouts (Pages and Templates) which seem to have inconsistent defaults anyway (Grid and List, respectively). Full disclosure: I prefer Table view on both, so having persistence once I set to these views would be amazing.
bacoords
commented
2 months ago +1 and this is making me wonder if we need a full "Visual State Persistence" tracking issue as this keeps coming up across the user interface (CC @annezazu)?
The site editor should consider including at least some ability to keep some of these visual views in some sort of state or local storage for each individual screen so that everything doesn't always get reset every time you click into a single post object to edit it.
kubiqsk
commented
1 month ago I believe that everyone will be happy with a table layout as a default option everywhere, because this is crazy resources expensive to render all the block in all the templates once you click on Templates in sidepanel in Site Editor. I'm trying to find any solution for this, because people are getting really angry about freezing browsers...
oandregal
commented
1 month ago Added three more features (user choices) that would benefit from being persisted:
In the default views e.g. 'All templates' there are certain configurable options that you'd expect to persist across sessions. For example changing the number of rows per page, or the fields that are displayed. Currently this is not the case.
It would be good to start by making the layout, rows per page, and field display options persistent. This would be consistent with the 'Screen options' on the All Posts / All Pages views in wp-admin.
Let's explore whether sorting should also persist separately. I didn't include it here because wp-admin sorting is not persistent.