-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent List View tracking issue #29736
Comments
Seems like a great enhancement to me (and @Copons seems to agree as well 🙂 ) Added to the list! 👍 |
I've updated the issue mentioning #31047, which is the PR that adds the persistent list view to the post editor. |
@simison I'm not familiar with the Widgets editor, but it should be fairly easy from a code standpoint (see #31047). Of course, I can absolutely help with that if needed. |
Cc @draganescu for thoughts on above. |
Although it doesn't seem like the Widgets Editor hierarchy will usually grow as big as the Post or Site Editor's, it would be good to add it even if it is from a UI consistency point of view. The priority in the Widgets Editor before and after feature freeze is stabilizing it as much as possible, but let's keep it in mind in #32311 👍 |
I've created an issue for improving e2e test coverage of List View - #38774. |
Is there currently a way (even via code snippet) to force List View to always be open by default? |
I've written up a fresh issue to look at some of the current usability tasks for the list view over in #49563. While there are still some outstanding tasks in this issue, it's also quite an old one, and after chatting with @talldan, it sounds like it might be a good time to close out this particular tracking issue. Feel free to re-open this issue, though, if anyone would prefer to keep this one going! |
The Persistent List View will benefit as well from the improvements done to the List View feature as collected in #29733
Milestone 1 - First implementation
Milestone 2 - Refinement and usability enhancements
Milestone 3 - Further improvements.
The text was updated successfully, but these errors were encountered: