[wp-trac] [WordPress Trac] #51506: Add new block widgets editor
WordPress Trac
noreply at wordpress.org
Tue Oct 20 07:07:56 UTC 2020
#51506: Add new block widgets editor
-----------------------------+-------------------------
Reporter: isabel_brison | Owner: noisysocks
Type: enhancement | Status: accepted
Priority: normal | Milestone: 5.7
Component: Widgets | Version:
Severity: normal | Resolution:
Keywords: has-patch early | Focuses:
-----------------------------+-------------------------
Comment (by paaljoachim):
I believe what is being said above here is that the new widget screen will
not take over the existing core widget screen in 5.6, but be punted to
early 5.7.
I breath a sigh of relief, because the new widget screen needs a lot more
testing out in the wild before it suddenly becomes the new default screen
in core. We need to get it working properly with the user interface, user
flow and functions testing it in the Gutenberg plugin. It also needs to
fully work with the customizer (and also Full Site Editing) before a
totally new experience of using widgets can be incorporated into core. As
beta 1 is today I was a bit worried that a not fully tested and
functioning feature was on its way into core. I am glad to hear that we
are holding off on including the new widget screen. In the mean time we
still need to get it working for people who use the Gutenberg plugin.
In relation with helping the user feel secure....
We need to make sure that a user can easily switch between a new
(experimental) screen that has become default using the Gutenberg plugin
to the old widget screen. As in having a button or another easy way to
switch between new <-> old screen. Atleast for a while. (Something to
remember for the Navigation screen when that becomes the new default nav
screen in the Gutenberg plugin.) I believe at present stage we were
forcing the user who does not have a correct functioning widget screen to
add code to the functions file to get the old widget screen back. Many
users feel uncomfortable adding code to the functions file. One can
perhaps force the user to do so when a widget screen is ready and bugs
have been fixed, but not when it in a sense is still in a testing phase.
It makes the user feel worried about using the Gutenberg plugin when an
experimental feature has become default when it really should have been
experimental a while longer.
Thank you for holding off on incorporating the new widget screen into 5.6!
Punting it into an early 5.7 phase feels like the correct move.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/51506#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list