-
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
Widgets Editor Tracking Issue #24687
Comments
Updated to reflect the new focus on Backwards compatibility and extensibility. |
Updated by @noisysocks to reflect priorities for a good merge candidate for WP 5.8. |
I have updated this issue with new info (props @noisysocks) about blockers as we head into the code freeze for WP 5.8 RC 1. |
Hey! It's WordPress 5.8 RC2! Can you believe this? WIdgets are going to live nicely along with blocks thanks to the feature this issue tracked for so long! Thanks everyone for the great work. 🎉 🙏🏻 Closing this as it has run its course. Let's track #33242 instead and make things even better! |
Last updated June 23, 2021
Extends #24551, preliminary for milestone 7
This is an overview issue that we'll maintain going forward into the 5.8 milestone. It attempts to track discussions and resulting actions about the Widgets Editor.
This overview tries not to track bugs of the Widgets Editor, for that you should filter open issues using the labels [Feature] Widgets Screen and [Type]Bug.
🏷 Important to do before 5.8 RC 1
Blockers for launching the Widgets Editor in WP 5.8
Widgets Screen
wp.editor.initialize
is not a function notice Core-53437This bug prevents legacy widgets such as Text from working which is a blocker. Has a (hacky) patch.
This bug prevents themes from opting out of the block editor which is a blocker. Has a patch.
This bug prevents widgets in LegacyWidget block to render properly. Has patch from @spacedmonkey.
This bug prevents FSE blocks from working properly.
Blockers for making the Widgets Editor opt-out in WP 5.8
Backwards compatibility
Widget screen
This bug means that two of the default blocks you see in a new WordPress install look broken in the widgets screen and customizer. Needs an assignee.
This is an alternative to the above. It’s more work and so perhaps not feasible for 5.8 but provides quite a nice UX as it makes widgets more WYSIWYG. @tellthemachines is looking into it.
🏷 Regular priority
Widgets in Customizer
The widgets editor in the Customizer should have a smooth user experience and be enabled by default.
Blocks in Customizer: Implement block inspector panel #29286The inspector in the widgets customizer should follow accessibility best practices #30271 Widgets: Refactor the inspector in Widgets Customizer to use core's controls #30431__unstable_instance
hack Widgets in Customizer: Remove temporary __unstable_instance hack #30266Legacy Widget
Feature parity with the classic widgets screen
Widgets editor
Block support in widget areas
REST API
__experimentalBatch
to respect batch size limit Batch saving: Modify __experimentalBatch to respect batch size limit #28709sidebars
REST API endpoint. Create remaining issues out of this overview #24530The text was updated successfully, but these errors were encountered: