Title: Call for Testing the Widgets Screen in Gutenberg 9.1
Author: annezazu
Published: September 30, 2020
Last modified: February 10, 2021
---
[ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
5:29 pm _on_ September 30, 2020
Tags: [5.6 ( 85 )](https://make.wordpress.org/core/tag/5-6/),
[core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [widgets ( 26 )](https://make.wordpress.org/core/tag/widgets/)
# Call for Testing the Widgets Screen in Gutenberg 9.1
_Thank you to [@andraganescu](https://profiles.wordpress.org/andraganescu/) and
[@mapk](https://profiles.wordpress.org/mapk/) who collaborated with me on this post._
## Introducing the Widgets Screen
After the GutenbergGutenberg The Gutenberg project is the new Editor Interface for
WordPress. The editor improves the process and experience of creating new content,
making writing rich content much simpler. It uses ‘blocks’ to add richness rather
than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
8.9 release moved the new blockBlock Block is the abstract term used to describe
units of markup that, composed together, form the content or layout of a webpage
using the WordPress editor. The idea combines concepts of what in the past may have
achieved with shortcodes, custom HTML, and embed discovery into a single consistent
API and user experience. based Widgets Screen out of experimental status, Gutenberg
9.1 released today includes design updates that now put the project in a great spot
for a call for testing. This new functionality replaces the previous adminadmin (
and super admin) `Appearance > Widgets` screen.
Image showing the layout of the new Widgets Screen.
The new Widgets Screen both replicates the functionalities of the previous screen
and unlocks the ability to add blocks to widgetWidget A WordPress Widget is a small
block that performs a specific function. You can add these widgets in sidebars also
known as widget-ready areas on your web page. WordPress widgets were originally
created to provide a simple and easy-to-use way of giving design and structure control
of the WordPress theme to the user. areas (also called sidebars) in any theme that
supports this new screen.
Image showing the Inserter in the context of the new Widgets Screen.
## Help test this feature
This is a call for testing for this new feature. Please report your findings on
GithubGitHub GitHub is a website that offers online implementation of git repositories
that can easily be shared, copied and modified by other developers. Public repositories
are free to host, private repositories require a paid subscription. GitHub introduced
the concept of the ‘pull request’ where code changes done in branches by contributors
can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/)
in the [Gutenberg repository](http://github.com/wordpress/gutenberg) as issues or
in the comments below. If you have triagetriage The act of evaluating and sorting
bug reports, in order to decide priority, severity, and other factors. access, labeling
any issue with `[Feature] Widgets Screen` would be very helpful. Alternatively,
you can simply include `[Widgets screen]` in the title to help those who can set
the labels appropriately. Check out the instructions below for more detailed information.
Finally, testing should cover all the features you’d expect from the previous editor,
as the new one should offer “feature parity”, meaning all the things previously
available should still be available. Of note, it would be particularly helpful when
testing to focus on the feature of adding blocks alongside classic widgets and to
focus on any backward incompatibility issues that the block editor might introduce
in relation to using widgets in themes.
## Testing Flow
Here is a basic flow for testing:
1. Have a site using WordPress 5.5.
2. Make sure you use a theme that supports widget areas (e.g. TwentyTwenty).
3. Go to the website’s admin.
4. Install and activate the Gutenberg pluginPlugin A plugin is a piece of software
containing a group of functions that can be added to a WordPress website. They
can extend functionality or add new features to your WordPress websites. WordPress
plugins are written in the PHP programming language and integrate seamlessly with
WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party.. If you already have it installed,
make sure you are using at least Gutenberg 9.1.
5. Go to Appearance > Widgets.
6. Notice that it visually resembles the Block Editor now.
7. If you have a 3rd party widget installed, search for it in the Block Library and
add it.
8. Adjust any required settings and Preview your widget.
9. Now drag that Widget into another Widget Area on your screen.
10. Go back to the first Widget Area and add an Image block.
11. Below the Image block add a Latest Posts block.
12. Save your changes and view them on the frontend.
13. Go back to the Widget screen and drag the Image block into the “Inactive Widgets”
Area.
14. Save and check out the frontend of the website.
15. Share your experience in the comments below or [in GitHub directly](https://github.com/WordPress/gutenberg/issues).
What to notice:
* Did it crash?
* If it worked, did the editor perform as expected?
* Was it intuitive for you to add blocks and third party widgets (ie from other
plugins)?
* Did it work using Keyboard only?
* Did it work using a screen reader?
## Backward compatibility testing
The best way to test for backward compatibility issues is to install plugins that
provide widgets and try to add them to widget areas using the new Widgets Screen.
If you already have a website using widgets and you use the Gutenberg plugin, the
widgets you have set up should just appear in the new editor. Outside of testing
what you commonly install, try popular plugins that provide widgets and see if:
* The plugin widget can be added to any widget area.
* The plugin widget can be set up and customized in the new Widget Screen.
* The plugin widget renders well on the website’s frontend.
The new Widgets Screen is expected to introduce some backward incompatibility, mainly
because the block based editor does not contain the same HTMLHTML HyperText Markup
Language. The semantic scripting language primarily used for outputting content
in web browsers. as the previous screen. We do aim to support all of the previous
screen’s hooksHooks In WordPress theme and development, hooks are functions that
can be applied to an action or a Filter in WordPress. Actions are functions performed
when a certain event occurs in WordPress. Filters allow you to modify certain functions.
Arguments used to hook both filters and actions look the same., filters and actions,
in both the admin and the frontend, as these are the correct extension points for
WordPress.
## Extendability testing
The new Widgets Screen should prefer blocks over corresponding widgets. That means
that if a block is registered by a plugin and it covers the exact same role that
a widget currently has, the developer of the block can use the new `widgets_to_exclude_from_legacy_widget_block`
filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output. to add the widget they replaced with the new block to an exclusion list.
All the widgets that have block equivalents will not be available to use through
the LegacyWidget block.
Testing extendability should not focus solely on previous available hooks and filters
but also imagining new points of extensibility in the new block based Widgets Screen.
## Disabling the new Widgets Screen
Users of the plugin who do not want to test the new Widgets Screen or who require
the old screen, can use a simple filter to disable the new Widgets Screen. Just
place this in [your theme’s](https://developer.wordpress.org/themes/basics/theme-functions/)`
functions.php` file:
```wp-block-code
add_filter( 'gutenberg_use_widgets_block_editor', '__return_false', 100 );
```
## Thank you!
Thank you for helping with testing the new Widgets Screen! Since it is one of the
major focuses of WordPress 5.6 any help in this early stage is immensely valuable.
If you would like to suggest improvements to this call for testing, leave them in
the comments!
[#5-6](https://make.wordpress.org/core/tag/5-6/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/),
[#widgets](https://make.wordpress.org/core/tag/widgets/)
### Share this:
* [ Threads ](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/?share=threads)
* [ Mastodon ](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/?share=mastodon)
* [ Bluesky ](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/?share=bluesky)
* [ X ](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/?share=x)
* [ Facebook ](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/?share=facebook)
* [ LinkedIn ](https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/?share=linkedin)
1. 
2. [annezazu](https://profiles.wordpress.org/annezazu/) 6:21 pm _on_ September
30, 2020
3. +make.wordpress.orgWordPress.org The community site where WordPress code is created
and shared by the users. This is where you can download the source code for WordPress
core, plugins and themes as well as the central location for community conversations
and organization. [https://wordpress.org/](https://wordpress.org/)/accessibilityAccessibility
Accessibility (commonly shortened to a11y) refers to the design of products, devices,
services, or environments for people with disabilities. The concept of accessible
design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning
compatibility with a person’s assistive technology (for example, computer screen
readers). (https://en.wikipedia.org/wiki/Accessibility)/ worried this didn’t go
through for some reason so separating the cross post out.
+make.wordpress.org/
design/
4. 
5. [Mark Uraine](https://profiles.wordpress.org/mapk/) 10:39 pm _on_ October 6,
2020
6. I’ve been busting out some issues in GithubGitHub GitHub is a website that offers
online implementation of git repositories that can easily be shared, copied and
modified by other developers. Public repositories are free to host, private repositories
require a paid subscription. GitHub introduced the concept of the ‘pull request’
where code changes done in branches by contributors can be reviewed and discussed
before being merged by the repository owner. [https://github.com/](https://github.com/)
today for this! It’s looking so much better, but there are plenty of keyboard
navigation problems.
7. 
8. [Joy](https://profiles.wordpress.org/joyously/) 12:56 am _on_ October 7, 2020
9. Being used to the old drag and drop which makes the widgetWidget A WordPress Widget
is a small block that performs a specific function. You can add these widgets
in sidebars also known as widget-ready areas on your web page. WordPress widgets
were originally created to provide a simple and easy-to-use way of giving design
and structure control of the WordPress theme to the user. name the operative portion,
at first I thought I couldn’t drag in the new one. Having the drag area and the
arrows in the toolbar is a lot less intuitive.
Having all the widgets open by
default makes it difficult to see what’s going on. Is there a way to collapse
them all? I clicked on the 3 lines icon at the top and it shows just “Legacy Widget”
instead of the title or name. That’s worthless. I clicked on the + at the bottom
and without choosing anything, it adds a paragraph blockBlock Block is the abstract
term used to describe units of markup that, composed together, form the content
or layout of a webpage using the WordPress editor. The idea combines concepts
of what in the past may have achieved with shortcodes, custom HTML, and embed
discovery into a single consistent API and user experience., which shows in the
List View. This could be problematic for determining if a sidebarSidebar A sidebar
in WordPress is referred to a widget-ready area used by WordPress themes to display
information that is not a part of the main content. It is not always a vertical
column on the side. It can be a horizontal rectangle below or above the content
area, footer, header, or any where in the theme. is empty, as themes often use
a different layout if the sidebar is empty (at least my theme has code to check
this). I clicked on Preview for my theme’s custom widget and it shows “Fatal error:
Uncaught Error: Call to a member function render() on null in gutenbergGutenberg
The Gutenberg project is the new Editor Interface for WordPress. The editor improves
the process and experience of creating new content, making writing rich content
much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)/
lib/widget-preview-template.php:37”. And I had to type that because it wouldn’t
let me select that text.
10. I prefer the individual Save versus this new screen with one Update button. If
I wanted that, I’d use the CustomizerCustomizer Tool built into WordPress core
that hooks into most modern themes. You can use it to preview and modify many
of your site’s appearance settings. for widgets, but I never liked that interface.
11. The arrow on the top of the widget area never switches to indicate if it’s open
or closed.
I can’t drag a widget from the footer to the sidebar. Well, it didn’t
work at first because the widget area has to be open. That isn’t the case for
the legacy screen. When I dragged the Tag Cloud and happened to be over a Text
widget’s text area when I let go of it, the text went into the Text widget instead
of moving the Tag Cloud widget. When clicking on the + at the top, I expect to
see all my widgets first and blocks after that (and the prompt says “search for
a block” but we’re on the Widgets page). The widgets should be sorted like they
used to be. They don’t look sorted at all. The widget list shows one called Legacy
Widget. Is this from the GB pluginPlugin A plugin is a piece of software containing
a group of functions that can be added to a WordPress website. They can extend
functionality or add new features to your WordPress websites. WordPress plugins
are written in the PHP programming language and integrate seamlessly with WordPress.
These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party.? Why is that name shown in the
List View, when my custom widgets show the correct name in the widget list? Just
like in the post editor, getting out of the + menu removes the right sidebar.
In this case, that’s not so bad, but it would make a better widget screen if you
left the + menu open all the time (or with a collapse button), and it would actually
be more like the old widget screen. I can’t drag from the list to the widget area,
which I can on the old screen.
12. It sure seems like it would be easier if you just add blocks to the existing widget
screen instead of messing around with making widgets into blocks (as if they aren’t
already blocks of content). Just one widget that renders any block sounds easy.(
Hint: I have a custom widget in my theme, for any template part.)
13. * 
* [Joy](https://profiles.wordpress.org/joyously/) 12:58 am _on_ October 7,
2020
* Oh, and it let me leave the page without saving … and no prompt to save.
* 
* [Mark Uraine](https://profiles.wordpress.org/mapk/) 5:37 pm _on_ October
7, 2020
* Thanks for the feedback, Joy!
* > Having all the widgets open by default makes it difficult to see what’s going
> on. Is there a way to collapse them all?
* This isn’t possible right now.
* > I clicked on the 3 lines icon at the top and it shows just “Legacy WidgetWidget
> A WordPress Widget is a small block that performs a specific function. You
> can add these widgets in sidebars also known as widget-ready areas on your
> web page. WordPress widgets were originally created to provide a simple and
> easy-to-use way of giving design and structure control of the WordPress theme
> to the user.” instead of the title or name.
* There’s an issue for this: [https://github.com/WordPress/gutenberg/issues/24940](https://github.com/WordPress/gutenberg/issues/24940)
* > I clicked on the + at the bottom and without choosing anything, it adds a
> paragraph blockBlock Block is the abstract term used to describe units of
> markup that, composed together, form the content or layout of a webpage using
> the WordPress editor. The idea combines concepts of what in the past may
> have achieved with shortcodes, custom HTML, and embed discovery into a single
> consistent API and user experience., which shows in the List View.
* I didn’t see this empty Paragraph block appear in the List View, and it doesn’t
look like it appears on the frontend either. I believe it’s there to provide
an insertion point to add content, much like the post editor.
* > The arrow on the top of the widget area never switches to indicate if it’s
> open or closed.
* It was switching for me. I’ll keep an eye out if it changes due to other factors.
* > I can’t drag a widget from the footer to the sidebarSidebar A sidebar in
> WordPress is referred to a widget-ready area used by WordPress themes to
> display information that is not a part of the main content. It is not always
> a vertical column on the side. It can be a horizontal rectangle below or
> above the content area, footer, header, or any where in the theme.. Well,
> it didn’t work at first because the widget area has to be open. That isn’t
> the case for the legacy screen.
* This has also been recorded here: [https://github.com/WordPress/gutenberg/issues/25911](https://github.com/WordPress/gutenberg/issues/25911)
* > When I dragged the Tag Cloud and happened to be over a Text widget’s text
> area when I let go of it, the text went into the Text widget instead of moving
> the Tag Cloud widget.
* That’s frustrating. Definitely a bugbug A bug is an error or unexpected result.
Performance improvements, code optimization, and are considered enhancements,
not defects. After feature freeze, only bugs are dealt with, with regressions(
adverse changes from the previous version) being the highest priority..
* > When clicking on the + at the top, I expect to see all my widgets first and
> blocks after that (and the prompt says “search for a block” but we’re on
> the Widgets page). The widgets should be sorted like they used to be.
* This is because you can now add blocks to these sections just as you would
widgets. Keeping the same order keeps consistency across editors. All 3rd party
widgets are listed under the “Widgets” categoryCategory The 'category' taxonomy
lets you group posts / content together that share a common bond. Categories
are pre-defined and broad ranging. in the Inserter.
* > The widget list shows one called Legacy Widget. Is this from the GB pluginPlugin
> A plugin is a piece of software containing a group of functions that can
> be added to a WordPress website. They can extend functionality or add new
> features to your WordPress websites. WordPress plugins are written in the
> PHP programming language and integrate seamlessly with WordPress. These can
> be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
> or can be cost-based plugin from a third-party.? Why is that name shown in
> the List View, when my custom widgets show the correct name in the widget
> list?
* I’m not sure it needs to be listed at all. Good question!
* > I can’t drag from the list to the widget area, which I can on the old screen.
* I believe this has been raised and is being looked into as well.
* Thanks for all this!
14. 
15. [Joy](https://profiles.wordpress.org/joyously/) 1:52 am _on_ October 7, 2020
16. I started over.
Entering the widgetWidget A WordPress Widget is a small block
that performs a specific function. You can add these widgets in sidebars also
known as widget-ready areas on your web page. WordPress widgets were originally
created to provide a simple and easy-to-use way of giving design and structure
control of the WordPress theme to the user. screen, the first widget area is open,
and the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area
used by WordPress themes to display information that is not a part of the main
content. It is not always a vertical column on the side. It can be a horizontal
rectangle below or above the content area, footer, header, or any where in the
theme. shows all the widget areas (erroneously called BlockBlock Block is the
abstract term used to describe units of markup that, composed together, form the
content or layout of a webpage using the WordPress editor. The idea combines concepts
of what in the past may have achieved with shortcodes, custom HTML, and embed
discovery into a single consistent API and user experience. areas). When I click
on my Sidebar widget area in the sidebar, it positions that area at the bottom
of the window. The area itself is still closed. If it didn’t have the blue border,
I wouldn’t have known what happened. I clicked or hovered in between two widgets
in my Sidebar and got a + to appear (I was surprised), and added a Quote block,
wrote some text and saved. The block showed correctly in between the widgets.
I then dragged the Quote block up one widget and that showed correctly also. But
I deactivated the pluginPlugin A plugin is a piece of software containing a group
of functions that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written
in the PHP programming language and integrate seamlessly with WordPress. These
can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. to check the original Widget page(
I deleted a duplicate), and when I reactivated GB and went back the Quote block
was gone.
17. The borders on the legacy widgets look just like the ones on the toolbar. It would
be much better if they looked different, and were collapsible, like on the old
widget screen.
18. * 
* [Mark Uraine](https://profiles.wordpress.org/mapk/) 5:42 pm _on_ October
7, 2020
* > the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area
> used by WordPress themes to display information that is not a part of the
> main content. It is not always a vertical column on the side. It can be a
> horizontal rectangle below or above the content area, footer, header, or
> any where in the theme. shows all the widgetWidget A WordPress Widget is
> a small block that performs a specific function. You can add these widgets
> in sidebars also known as widget-ready areas on your web page. WordPress
> widgets were originally created to provide a simple and easy-to-use way of
> giving design and structure control of the WordPress theme to the user. areas(
> erroneously called BlockBlock Block is the abstract term used to describe
> units of markup that, composed together, form the content or layout of a
> webpage using the WordPress editor. The idea combines concepts of what in
> the past may have achieved with shortcodes, custom HTML, and embed discovery
> into a single consistent API and user experience. areas). When I click on
> my Sidebar widget area in the sidebar, it positions that area at the bottom
> of the window.
* Got it logged:
[https://github.com/WordPress/gutenberg/issues/25745#issuecomment-705016495](https://github.com/WordPress/gutenberg/issues/25745#issuecomment-705016495)
* > and when I reactivated GB and went back the Quote block was gone.
* Good catch. If it’s a static block, I would expect the HTMLHTML HyperText Markup
Language. The semantic scripting language primarily used for outputting content
in web browsers. to remain regardless, right? But that would probably mean
that the HTML from the block, when pluginPlugin A plugin is a piece of software
containing a group of functions that can be added to a WordPress website. They
can extend functionality or add new features to your WordPress websites. WordPress
plugins are written in the PHP programming language and integrate seamlessly
with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. is turned off, should be converted
into an HTML widget? What do you think?
19. 
20. [Joy](https://profiles.wordpress.org/joyously/) 2:06 am _on_ October 7, 2020
21. One more thing: the widgetWidget A WordPress Widget is a small block that performs
a specific function. You can add these widgets in sidebars also known as widget-
ready areas on your web page. WordPress widgets were originally created to provide
a simple and easy-to-use way of giving design and structure control of the WordPress
theme to the user. area description is not shown anywhere.
And now that I noticed
that, I see that the widget description is not shown anywhere either. And clicking
on my widget to check that it’s not shown when clicked (it’s not), the widget
was inserted (somewhere) but it’s not in view. I can see the lower part of a toolbar
though. Scrolling up I find it at the top and wonder if that’s the one I just
clicked on. I assume it is since it has a blue outline. I clicked on the undo
button but nothing happens.
22. * 
* [Mark Uraine](https://profiles.wordpress.org/mapk/) 5:45 pm _on_ October
7, 2020
* > I see that the widgetWidget A WordPress Widget is a small block that performs
> a specific function. You can add these widgets in sidebars also known as
> widget-ready areas on your web page. WordPress widgets were originally created
> to provide a simple and easy-to-use way of giving design and structure control
> of the WordPress theme to the user. description is not shown anywhere either.
* Got it: [https://github.com/WordPress/gutenberg/issues/25190](https://github.com/WordPress/gutenberg/issues/25190)
23. 
24. [annezazu](https://profiles.wordpress.org/annezazu/) 5:49 pm _on_ October 7,
2020
25. +make.wordpress.org/test/
26. 
27. [Garrett Hyder](https://profiles.wordpress.org/garrett-eclipse/) 2:00 am _on_
October 8, 2020
28. Some feedback from testing;
29. * On larger screens can the Add blockBlock Block is the abstract term used to
describe units of markup that, composed together, form the content or layout
of a webpage using the WordPress editor. The idea combines concepts of what
in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience. left side menu just be displayed
by default and let it stay after a block is added.
* Once the Add block menu is available can the [ + ] button become an x to indicate
it is now used to close the menu [ x ]
* Initially the ‘Edit’ looks like a button and not the selected view so I clicked
it a few times thinking it broken until I realized it was a toggle with the
preview. Would be nice to tie these two together as a slide control to indicate
which is active vs. Inactive better as the active state currently resembles
a button and the item you should click.
* Delete in an empty Verse block should remove it returning to the block above
it like a paragraph block does.
* The widgetWidget A WordPress Widget is a small block that performs a specific
function. You can add these widgets in sidebars also known as widget-ready
areas on your web page. WordPress widgets were originally created to provide
a simple and easy-to-use way of giving design and structure control of the
WordPress theme to the user. accordion chevrons should flip on closing to indicate
click to open. Currently they are always pointed up.
* Would be a nice touch to allow drag and drop of new blocks from the left block
menu into the widget sections as widget users are accustom to the drag-drop
from the legacy system.
* An improvement on the list view would be to have all sidebarSidebar A sidebar
in WordPress is referred to a widget-ready area used by WordPress themes to
display information that is not a part of the main content. It is not always
a vertical column on the side. It can be a horizontal rectangle below or above
the content area, footer, header, or any where in the theme. sections available
but only the current expanded, this allows you to select other sidebars to
view their contents and event click to go edit them from that context.
* It would be nice to introduce a preview capabilitycapability A **capability**
is permission to perform one or more types of task. Checking if a user has
a capability is performed by the `current_user_can` function. Each user of
a WordPress site might have some permissions but not others, depending on their
role. For example, users who have the Author role usually have permission to
edit their own posts (the “edit_posts” capability), but not permission to edit
other users’ posts (the “edit_others_posts” capability). to the sidebar sections
as a whole so you can preview the entire sidebar to see how the widgets interact
visually without having to click each one’s Preview individually. Maybe have
it up with the Update button and just switches all blocks to preview mode.
* You shouldn’t be able to create new inactive widgets, only drag existing ones
into it or when sidebars are removed they’ll end up there.
* Provide ability to clear inactive widgets, this was available in legacy.
* Can you still manage via Live Preview? If so a button for that was on the legacy
system.
* Undo should only become available once an action has ben taken.
* Will Legacy Widgets be available under a specific categoryCategory The 'category'
taxonomy lets you group posts / content together that share a common bond.
Categories are pre-defined and broad ranging. in the block inserter? Would
be nice to have them the top items for existing users so they don’t feel lost.
* The Legacy Widget just says ‘There are no widgets available.
* It would be nice if when you have a widget/block in your clipboard and you
go to the inserter to provide a paste option.
* I can’t seem to get Move To to work, I click it then go to click where I want
to move it to and get a blue line and can’t get the widget to move.
30. * 
* [Monika Rao](https://profiles.wordpress.org/monikarao/) 6:14 am _on_ October
14, 2020
* Some Feedback from Testing:
- Capitalize BlockBlock Block is the abstract term used to describe units
of markup that, composed together, form the content or layout of a webpage
using the WordPress editor. The idea combines concepts of what in the past
may have achieved with shortcodes, custom HTML, and embed discovery into
a single consistent API and user experience. areas string – [https://a.cl.ly/jkuDZJr8](https://a.cl.ly/jkuDZJr8)
- Need Breathing space on List Block – [https://a.cl.ly/o0um8kyQ](https://a.cl.ly/o0um8kyQ)
- Not able to drag the block at the end of the widgetWidget A WordPress Widget
is a small block that performs a specific function. You can add these widgets
in sidebars also known as widget-ready areas on your web page. WordPress
widgets were originally created to provide a simple and easy-to-use way
of giving design and structure control of the WordPress theme to the user.
area – [https://a.cl.ly/nOunkYEX](https://a.cl.ly/nOunkYEX)
- Need to highlight Widget area name – [https://a.cl.ly/xQuAL9lb](https://a.cl.ly/xQuAL9lb)
- Not able to drag the Image Block in Inactive Widget – [https://a.cl.ly/L1uQJzx5](https://a.cl.ly/L1uQJzx5)
- Scroll bar on selecting the Block Areas – [https://a.cl.ly/9ZuBXYrx](https://a.cl.ly/9ZuBXYrx)
- There should be a collapsible Icon for each block Area – [https://a.cl.ly/llu2Yzz7](https://a.cl.ly/llu2Yzz7)(
It uncessary increase scroll on my page)
* Backward Compatibility
- When I activated GutenbergGutenberg The Gutenberg project is the new Editor
Interface for WordPress. The editor improves the process and experience
of creating new content, making writing rich content much simpler. It uses‘
blocks’ to add richness rather than shortcodes, custom HTML etc.
[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
PluginPlugin A plugin is a piece of software containing a group of functions
that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written
in the PHP programming language and integrate seamlessly with WordPress.
These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party.
- Refresh the Widgets Page
- It stays the same, I couldn’t find the new changes on the page
* [https://a.cl.ly/L1uQJzzN](https://a.cl.ly/L1uQJzzN)
Product SidebarSidebar
A sidebar in WordPress is referred to a widget-ready area used by WordPress
themes to display information that is not a part of the main content. It is
not always a vertical column on the side. It can be a horizontal rectangle
below or above the content area, footer, header, or any where in the theme.
is missing when switching on the new interface Old Interface – [https://a.cl.ly/6quPe0Dk](https://a.cl.ly/6quPe0Dk)
New – [https://a.cl.ly/2Nujy2Ar](https://a.cl.ly/2Nujy2Ar)
- 
- [Mark Uraine](https://profiles.wordpress.org/mapk/) 8:08 pm _on_ October
14, 2020
- Thanks for the feedback, Monika!
- > Capitalize BlockBlock Block is the abstract term used to describe units
> of markup that, composed together, form the content or layout of a webpage
> using the WordPress editor. The idea combines concepts of what in the
> past may have achieved with shortcodes, custom HTML, and embed discovery
> into a single consistent API and user experience. areas string
- This is going to be changed to “WidgetWidget A WordPress Widget is a small
block that performs a specific function. You can add these widgets in sidebars
also known as widget-ready areas on your web page. WordPress widgets were
originally created to provide a simple and easy-to-use way of giving design
and structure control of the WordPress theme to the user. areas” soon. We’ve
been moving to Sentence case throughout, but I’m still uncertain if “areas”
should be capitalized or not.
- > Need Breathing space on List Block
- Recorded: [https://github.com/WordPress/gutenberg/issues/26127](https://github.com/WordPress/gutenberg/issues/26127)
- > Not able to drag the block at the end of the widget area.
> Not able to
> drag the Image Block in Inactive Widget.
- Several drag and drop issues have been recorded.
- > Need to highlight Widget area name
- I’d love to learn more why you think this is necessary.
- > Scroll bar on selecting the Block Areas
- This particular interaction will be going away. [https://github.com/WordPress/gutenberg/issues/25745](https://github.com/WordPress/gutenberg/issues/25745)
- > There should be a collapsible Icon for each block Area – [https://a.cl.ly/llu2Yzz7](https://a.cl.ly/llu2Yzz7)(
> It uncessary increase scroll on my page)
- The desired concept here is that once the widget forms are filled out, the
block shows the Preview state when unselected. This should remove any need
to collapse the widget.
- > When I activated GutenbergGutenberg The Gutenberg project is the new Editor
> Interface for WordPress. The editor improves the process and experience
> of creating new content, making writing rich content much simpler. It
> uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
>
> [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) PluginPlugin
> A plugin is a piece of software containing a group of functions that can
> be added to a WordPress website. They can extend functionality or add
> new features to your WordPress websites. WordPress plugins are written
> in the PHP programming language and integrate seamlessly with WordPress.
> These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
> or can be cost-based plugin from a third-party. Refresh the Widgets Page
> It stays the same, I couldn’t find the new changes on the page
- Definitely a bugbug A bug is an error or unexpected result. Performance
improvements, code optimization, and are considered enhancements, not defects.
After feature freeze, only bugs are dealt with, with regressions (adverse
changes from the previous version) being the highest priority..
* 
* [Joy](https://profiles.wordpress.org/joyously/) 6:19 pm _on_ October 14,
2020
* > You shouldn’t be able to create new inactive widgets, only drag existing
> ones into it or when sidebars are removed they’ll end up there.
* Yes, you can on the legacy screen, because you can configure the widgetWidget
A WordPress Widget is a small block that performs a specific function. You
can add these widgets in sidebars also known as widget-ready areas on your
web page. WordPress widgets were originally created to provide a simple and
easy-to-use way of giving design and structure control of the WordPress theme
to the user. first and then assign it to the widget area later.
* 
* [Mark Uraine](https://profiles.wordpress.org/mapk/) 7:37 pm _on_ October
14, 2020
* Thanks, Garrett! For posterity purposes, if any of your points have existing
issues created, I’m linking them in the replies so other might see as well.
* > On larger screens can the Add blockBlock Block is the abstract term used
> to describe units of markup that, composed together, form the content or
> layout of a webpage using the WordPress editor. The idea combines concepts
> of what in the past may have achieved with shortcodes, custom HTML, and embed
> discovery into a single consistent API and user experience. left side menu
> just be displayed by default and let it stay after a block is added.
> Once
> the Add block menu is available can the [ + ] button become an x to indicate
> it is now used to close the menu [ x ]
* The Add block menu (Inserter) works as a modal for keyboard users. This means
that as soon as the focus leaves, it closes. I don’t think we can change it.
The discussion can be read here: [https://github.com/WordPress/gutenberg/pull/24822](https://github.com/WordPress/gutenberg/pull/24822)
* Changing the + to an x is possible and discussed here: [https://github.com/WordPress/gutenberg/issues/22871#issuecomment-638625689](https://github.com/WordPress/gutenberg/issues/22871#issuecomment-638625689)
* > Initially the ‘Edit’ looks like a button and not the selected view
* Currently, this is how the “active” or toggled “on” elements display in GutenbergGutenberg
The Gutenberg project is the new Editor Interface for WordPress. The editor
improves the process and experience of creating new content, making writing
rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes,
custom HTML etc.
[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
related screens.
* > Delete in an empty Verse block should remove it returning to the block above
> it like a paragraph block does.
* We’ll need to get this logged as a block specific problem.
* > The widgetWidget A WordPress Widget is a small block that performs a specific
> function. You can add these widgets in sidebars also known as widget-ready
> areas on your web page. WordPress widgets were originally created to provide
> a simple and easy-to-use way of giving design and structure control of the
> WordPress theme to the user. accordion chevrons should flip on closing to
> indicate click to open. Currently they are always pointed up.
* This is the second time I’ve heard this, but the arrows flip for me. Can you
tell me what browser and Gutenberg version you tested on?
* > Would be a nice touch to allow drag and drop of new blocks from the left
> block menu
* Yes. yes. I believe this is planned. Some of this is discussed here: [https://github.com/WordPress/gutenberg/issues/22319](https://github.com/WordPress/gutenberg/issues/22319)
* > An improvement on the list view would be to have all sidebarSidebar A sidebar
> in WordPress is referred to a widget-ready area used by WordPress themes
> to display information that is not a part of the main content. It is not
> always a vertical column on the side. It can be a horizontal rectangle below
> or above the content area, footer, header, or any where in the theme. sections
> available but only the current expanded, this allows you to select other
> sidebars to view their contents and event click to go edit them from that
> context.
* This was raised here: [https://github.com/WordPress/gutenberg/issues/24940](https://github.com/WordPress/gutenberg/issues/24940)
* > It would be nice to introduce a preview capabilitycapability A **capability**
> is permission to perform one or more types of task. Checking if a user has
> a capability is performed by the `current_user_can` function. Each user of
> a WordPress site might have some permissions but not others, depending on
> their role. For example, users who have the Author role usually have permission
> to edit their own posts (the “edit_posts” capability), but not permission
> to edit other users’ posts (the “edit_others_posts” capability). to the sidebar
> sections as a whole so you can preview the entire sidebar to see how the
> widgets interact visually without having to click each one’s Preview individually.
* Ideally, once the widget form is filled in, I’d like it so that the widget
defaults to the Preview mode when unselected. This would provide more of a
Gutenberg feel.
* > Provide ability to clear inactive widgets, this was available in legacy.
* Does “clear” mean delete them from the area? If so, this can be done by selecting
them all and clicking delete.
* > Can you still manage via Live Preview? If so a button for that was on the
> legacy system.
* I don’t think so. If you can preview in the editor, is that enough?
* > Undo should only become available once an action has ben taken.
* Issue created: [https://github.com/WordPress/gutenberg/issues/26124](https://github.com/WordPress/gutenberg/issues/26124)
* > Will Legacy Widgets be available under a specific categoryCategory The 'category'
> taxonomy lets you group posts / content together that share a common bond.
> Categories are pre-defined and broad ranging. in the block inserter?
* Yes. They are under the “Widgets” category.
* > The Legacy Widget just says ‘There are no widgets available.
* If you have 3rd party widgets installed and have added the Legacy Widget block
to your area, the block should show a dropdown that allows you to select from
any of your 3rd party widgets.
* > I can’t seem to get Move To to work
* Issue recorded here: [https://github.com/WordPress/gutenberg/issues/25766](https://github.com/WordPress/gutenberg/issues/25766)
- 
- [Garrett Hyder](https://profiles.wordpress.org/garrett-eclipse/) 7:35
am _on_ October 17, 2020
- Much appreciated [@mapk](https://profiles.wordpress.org/mapk/) I’ve followed
the links there.
- > Initially the ‘Edit’ looks like a button and not the selected view
> >
> | – Currently, this is how the “active” or toggled “on” elements display
> in GutenbergGutenberg The Gutenberg project is the new Editor Interface
> for WordPress. The editor improves the process and experience of creating
> new content, making writing rich content much simpler. It uses ‘blocks’
> to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
> related screens. Currently the UIUI User interface here feels like it
> could use some work so I opened; [https://github.com/WordPress/gutenberg/issues/26229](https://github.com/WordPress/gutenberg/issues/26229)
- > Delete in an empty Verse blockBlock Block is the abstract term used to
> describe units of markup that, composed together, form the content or
> layout of a webpage using the WordPress editor. The idea combines concepts
> of what in the past may have achieved with shortcodes, custom HTML, and
> embed discovery into a single consistent API and user experience. should
> remove it returning to the block above it like a paragraph block does.
>
> > | – We’ll need to get this logged as a block specific problem. Created–
> [https://github.com/WordPress/gutenberg/issues/26230](https://github.com/WordPress/gutenberg/issues/26230)
- > The widgetWidget A WordPress Widget is a small block that performs a specific
> function. You can add these widgets in sidebars also known as widget-ready
> areas on your web page. WordPress widgets were originally created to provide
> a simple and easy-to-use way of giving design and structure control of
> the WordPress theme to the user. accordion chevrons should flip on closing
> to indicate click to open. Currently they are always pointed up.
> > | –
> This is the second time I’ve heard this, but the arrows flip for me. Can
> you tell me what browser and Gutenberg version you tested on? I’m using
> Mac 10.15.7, WP trunktrunk A directory in Subversion containing the latest
> development code in preparation for the next major release cycle. If you
> are running "trunk", then you are on the latest revision., Gutenberg 9.1.1,
> Firefox 80.0.1&81.0.2, Chrome 86.0.4240.75 and Safari 14.0. All three
> browsers hold the same issue.
- > It would be nice to introduce a preview capabilitycapability A **capability**
> is permission to perform one or more types of task. Checking if a user
> has a capability is performed by the `current_user_can` function. Each
> user of a WordPress site might have some permissions but not others, depending
> on their role. For example, users who have the Author role usually have
> permission to edit their own posts (the “edit_posts” capability), but
> not permission to edit other users’ posts (the “edit_others_posts” capability).
> to the sidebarSidebar A sidebar in WordPress is referred to a widget-ready
> area used by WordPress themes to display information that is not a part
> of the main content. It is not always a vertical column on the side. It
> can be a horizontal rectangle below or above the content area, footer,
> header, or any where in the theme. sections as a whole so you can preview
> the entire sidebar to see how the widgets interact visually without having
> to click each one’s Preview individually.
> > | – Ideally, once the widget
> form is filled in, I’d like it so that the widget defaults to the Preview
> mode when unselected. This would provide more of a Gutenberg feel. It
> would be nice to either default the widget blocks to preview mode, or
> provide a preview ability to view ALL blocks in preview. Ticketticket
> Created for both bug reports and feature development on the bug tracker.–
> [https://github.com/WordPress/gutenberg/issues/26231](https://github.com/WordPress/gutenberg/issues/26231)
- > Provide ability to clear inactive widgets, this was available in legacy.
>
> > | – Does “clear” mean delete them from the area? If so, this can be
> done by selecting them all and clicking delete. Feature Requestfeature
> request A feature request should generally begin the process in the ideas
> forum, on a mailing list, as a plugin, or brought to the attention of
> the core team, such as through scope meetings held for each major release.
> Unsolicited tickets of this variety are typically, therefore, discouraged.–
> [https://github.com/WordPress/gutenberg/issues/26232](https://github.com/WordPress/gutenberg/issues/26232)
- > The Legacy Widget just says ‘There are no widgets available.
> > | – If
> you have 3rd party widgets installed and have added the Legacy Widget
> block to your area, the block should show a dropdown that allows you to
> select from any of your 3rd party widgets. Feature Request – [https://github.com/WordPress/gutenberg/issues/26240](https://github.com/WordPress/gutenberg/issues/26240)
- A few new items from further testing;
* Updating Widgets should ‘Dirty’ the site so that going to customizerCustomizer
Tool built into WordPress core that hooks into most modern themes. You
can use it to preview and modify many of your site’s appearance settings.
doesn’t load the starter content.
- Bug – [https://github.com/WordPress/gutenberg/issues/26241](https://github.com/WordPress/gutenberg/issues/26241)
* In Customizer > Widgets it would be nice to indicate what type of Block
it is instead of just ‘Block’.
- Feature – [https://github.com/WordPress/gutenberg/issues/26242](https://github.com/WordPress/gutenberg/issues/26242)
* From Customizer when going to edit the block take them and focus on said
block in the editor.
- Feature – [https://github.com/WordPress/gutenberg/issues/26243](https://github.com/WordPress/gutenberg/issues/26243)
- One item I didn’t ticket because it’s more an open question;
Can we not
edit blocks in the customizer? Should we remove widget editing in the customizer?
- Appreciate all the responses if I didn’t address above it’s because your
response was great and no more action was needed.
- Cheers
* 
* [Garrett Hyder](https://profiles.wordpress.org/garrett-eclipse/) 7:
39 am _on_ October 17, 2020
* > Can you still manage via Live Preview? If so a button for that was
> on the legacy system.
> I don’t think so. If you can preview in the
> editor, is that enough?
* Oops I missed one;
[https://github.com/WordPress/gutenberg/issues/26244](https://github.com/WordPress/gutenberg/issues/26244)
31. 
32. [Hanna](https://profiles.wordpress.org/hannairis/) 8:16 am _on_ October 14,
2020
33. Some questions based on testing:
34. * Is there a way to keep the Widgets selector area (Left side) always open? When
you add a widgetWidget A WordPress Widget is a small block that performs a
specific function. You can add these widgets in sidebars also known as widget-
ready areas on your web page. WordPress widgets were originally created to
provide a simple and easy-to-use way of giving design and structure control
of the WordPress theme to the user./blockBlock Block is the abstract term used
to describe units of markup that, composed together, form the content or layout
of a webpage using the WordPress editor. The idea combines concepts of what
in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience. to a block area, the selector
area auto-closes. If I wanted to quickly add say 5-10 individual widgets, currently
I’d have to do a lot of back-and-forth clicking and scrolling.
35. There is an option to search for a widget directly on the widget area, but that
assumes you know what to search for (as it doesn’t list all widgets).
36. * Is there a way to change the order of the Widgets “categories” (Text, Media,
Design, Widgets, Embeds) in the widgets selector (left side)? If you only wanted
to work with say the last two sections, that’s a lot of scrolling down.
37. * Calendar widget (on backend) shows warning message _“This block has encountered
an error and cannot be previewed.”_, but the calendar widget itself seems to
work on frontend.
38. Is this meant to be a warning that there’s no preview, but there’s no actual error(
other than the no-preview itself)? If that’s the case, I’d prefer a more accurate
warning text.
39. * Will `.wp-block-` blocks add native support for `.widget` class or will official
themes add support or will there be no backward compatibility? Example: Twenty
Nineteen theme uses `.widget` to set the widts:
40. ```notranslate
#colophon .widget-column .widget {
margin-right: calc(3 * 1rem);
width: calc(50% - ( 3 * 1rem ));
}
```
41. The new `wp-block-calendar` is missing the class/rule, so widgets don’t appear
as 50%, but instead use their default (content) width.
42. * 
* [Mark Uraine](https://profiles.wordpress.org/mapk/) 8:25 pm _on_ October
14, 2020
* Hi Hanna! Wonderful questions!
* > Is there a way to keep the Widgets selector area (Left side) always open?
* There is not. The reason it closes is because it behaves as a modal and for
keyboard interactions, it disappears when unselected.
* > There is an option to search for a widgetWidget A WordPress Widget is a small
> block that performs a specific function. You can add these widgets in sidebars
> also known as widget-ready areas on your web page. WordPress widgets were
> originally created to provide a simple and easy-to-use way of giving design
> and structure control of the WordPress theme to the user. directly on the
> widget area, but that assumes you know what to search for (as it doesn’t
> list all widgets).
* Good point. Maybe we should add the “Browse all” option here as we have it
in the Post Editor.
* > Is there a way to change the order of the Widgets “categories” (Text, Media,
> Design, Widgets, Embeds) in the widgets selector (left side)? If you only
> wanted to work with say the last two sections, that’s a lot of scrolling
> down.
* No way to change the order, sorry.
* > Calendar widget (on backend) shows warning message “This blockBlock Block
> is the abstract term used to describe units of markup that, composed together,
> form the content or layout of a webpage using the WordPress editor. The idea
> combines concepts of what in the past may have achieved with shortcodes,
> custom HTML, and embed discovery into a single consistent API and user experience.
> has encountered an error and cannot be previewed.”, but the calendar widget
> itself seems to work on frontend.
* Sounds like a bugbug A bug is an error or unexpected result. Performance improvements,
code optimization, and are considered enhancements, not defects. After feature
freeze, only bugs are dealt with, with regressions (adverse changes from the
previous version) being the highest priority..
- 
- [Hanna](https://profiles.wordpress.org/hannairis/) 7:14 am _on_ October
15, 2020
- Thank you for these, Mark.
- For the last issue of themes and `.wp-block-` and `.widget` use – will the
backwards compability be addressed at GutenbergGutenberg The Gutenberg project
is the new Editor Interface for WordPress. The editor improves the process
and experience of creating new content, making writing rich content much
simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
HTML etc.
[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
level (eg add the `widget` class) or up to individual theme authors?
- By this I mean for example turning:
- ```notranslate
```
- into:
- ```notranslate
```
- Or would theme authors be responsible for fixing any CSSCSS Cascading Style
Sheets. issues?
* 
* [Mark Uraine](https://profiles.wordpress.org/mapk/) 6:26 pm _on_ October
15, 2020
* I believe this has been solved in this issue: [https://github.com/WordPress/gutenberg/issues/25174](https://github.com/WordPress/gutenberg/issues/25174)
and with this PR: [https://github.com/WordPress/gutenberg/pull/25693](https://github.com/WordPress/gutenberg/pull/25693)
* If I’m not understanding correctly, please pingPing The act of sending
a very small amount of data to an end point. Ping is used in computer
science to illicit a response from a target server to test it’s connection.
Ping is also a term used by Slack users to @ someone or send them a direct
message (DM). Users might say something along the lines of “Ping me when
the meeting starts.” me in SlackSlack Slack is a Collaborative Group
Chat Platform [https://slack.com/](https://slack.com/). The WordPress
community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
and we can work through this more.
- 
- [Hanna](https://profiles.wordpress.org/hannairis/) 10:35 am _on_
October 21, 2020
- This was just what I meant – tested with the latest 9.2.0 and all
good!
43. 
44. [Allie Nimmons](https://profiles.wordpress.org/alliennimmons/) 4:01 pm _on_
October 16, 2020
45. Summary of issues/feedback from 10/16 scrub in #coreCore Core is the set of software
required to run WordPress. The Core Development Team builds WordPress..
46. 1. Not being able to drag a widgetWidget A WordPress Widget is a small block that
performs a specific function. You can add these widgets in sidebars also known
as widget-ready areas on your web page. WordPress widgets were originally created
to provide a simple and easy-to-use way of giving design and structure control
of the WordPress theme to the user. from one widget area to another, so having
more than one is good to test that.
47. 2. You need to re-activate Inactive widget input field after you remove some text:
start typing “seo” – no widget appear (as you need to search with “/seo”)
48. * start removing “seo” with backspace
* after last clicking on backspace the whole input form is gone
* you need to re-activate the form to be able to type again
* start typing “/seo” – now finally blocks appear
49. ([video](https://wordpress.slack.com/archives/C02RQBWTW/p1602857356158000))
50. 3. Preview of Inactive widgets is not working. (Issue has already been documented
in a few places. [https://github.com/WordPress/gutenberg/issues/26040](https://github.com/WordPress/gutenberg/issues/26040)
and [https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+label%3A](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+label%3A)“[
Feature]+Widgets+Screen”] and [https://github.com/WordPress/gutenberg/issues/26104](https://github.com/WordPress/gutenberg/issues/26104)
51. 4. If you Preview your widget, you cannot leave Preview mode if you wan to make
more changes for your widget. Only reload of the page set Preview to off. ([video](https://wordpress.slack.com/archives/C02RQBWTW/p1602858100168200?thread_ts=1602857627.162000&cid=C02RQBWTW))
52. 5. This blue line between widgets when you hover over other widgets in search
box? ([screenshot](https://wordpress.slack.com/archives/C02RQBWTW/p1602858459171800?thread_ts=1602857627.162000&cid=C02RQBWTW))
53. 6. I am stuck on Step 5. After going to Appearance > Widget I get a screen where
the existing widgets show an error, but they are present in the front-end. I can
see them in the Customiser ([screenshots](https://wordpress.slack.com/archives/C02RQBWTW/p1602858592173000?thread_ts=1602857627.162000&cid=C02RQBWTW))
54. 7. Categories widget doesn’t seem to have the ability to add a Title ([screenshot](https://wordpress.slack.com/archives/C02RQBWTW/p1602859270182200?thread_ts=1602857627.162000&cid=C02RQBWTW))
55. 8. Simple Social Icons pluginPlugin A plugin is a piece of software containing
a group of functions that can be added to a WordPress website. They can extend
functionality or add new features to your WordPress websites. WordPress plugins
are written in the PHP programming language and integrate seamlessly with WordPress.
These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. doesn’t create the needed widget,
and the legacy widget doesn’t work
56. 9. It would be also nice to make all widgets collapsible: you can get lost by
scrolling though widgets
57. 10. I’ve reported this elsewhere, but can someone else test the “SiteOrigin Widgets
Bundle”. On the latest master it doesn’t work at all for me, it seems like the
widget’s JavaScriptJavaScript JavaScript or JS is an object-oriented computer
programming language commonly used to create interactive effects within web browsers.
WordPress makes extensive use of JS for a better user experience. While PHP is
executed on the server, JS executes within a user’s browser.
[https://www.javascript.com](https://www.javascript.com/)
isn’t loaded. So things like its image blockBlock Block is the abstract term used
to describe units of markup that, composed together, form the content or layout
of a webpage using the WordPress editor. The idea combines concepts of what in
the past may have achieved with shortcodes, custom HTML, and embed discovery into
a single consistent API and user experience. don’t work. I think on the latest
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
The editor improves the process and experience of creating new content, making
writing rich content much simpler. It uses ‘blocks’ to add richness rather than
shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
plugin it doesn’t function at all, but it renders the interface at least on master.
58. 11. how changing of the block type is supposed to work for widgets? Especially“
transform to group” option. What is the use case behind? ([screenshot](https://wordpress.slack.com/archives/C02RQBWTW/p1602858653175100))
59. * 
* [Daisy Olsen](https://profiles.wordpress.org/daisyo/) 5:31 pm _on_ October
16, 2020
* Thank you so much for compiling this list! I’m working through what you’ve
shared here to ensure that everything has been captured – either verifying
that it’s already been reported or creating an issue if one is needed.
60. 
61. [Helen Hou-Sandi](https://profiles.wordpress.org/helen/) 3:12 am _on_ October
17, 2020
62. I was not able to join the test scrub earlier but just spent a couple hours testing
and will try to summarize all of the feedback I have (apologies for any duplication
I do of other comments and issues). Overall, I want to note that I basically exclusively
interact with widgets in the customizerCustomizer Tool built into WordPress core
that hooks into most modern themes. You can use it to preview and modify many
of your site’s appearance settings., where the combination of the edit jump links(
my fave!) and the live previewing make it an actual pleasant editing experience
as opposed to the “save and surprise” of the adminadmin (and super admin) screen.
I don’t necessarily _dislike_ the widgets-as-blocks screen, but I also don’t like
it enough to want to use it, blocks or no blocks.
63. * My primary usability blockerblocker A bug which is so severe that it blocks
a release. on an existing site or one that used starter content is the inability
to convert a text widgetWidget A WordPress Widget is a small block that performs
a specific function. You can add these widgets in sidebars also known as widget-
ready areas on your web page. WordPress widgets were originally created to
provide a simple and easy-to-use way of giving design and structure control
of the WordPress theme to the user. to blocks. It’s very confusing to me that
something like an audio blockBlock Block is the abstract term used to describe
units of markup that, composed together, form the content or layout of a webpage
using the WordPress editor. The idea combines concepts of what in the past
may have achieved with shortcodes, custom HTML, and embed discovery into a
single consistent API and user experience. can be converted to a headerHeader
The header of your site is typically the first thing people will experience.
The masthead or header art located across the top of your page is part of the
look and feel of your website. It can influence a visitor’s opinion about your
content and you/ your organization’s brand. It may also look different on different
screen sizes. + audio, but I can’t convert a text widget that’s a simple header
+ sentence.
* My secondary usability issue (only behind the first by a little) is that the
legacy widgets actually display quite nicely in the preview, but you don’t
get that same kind of front-end-reflective styling in blocks, at least in Twenty
Twenty. When you combine that with the contextless editing on a separate screen,
I find it to be a pretty sub-par experience compared to the customizer.
* Another usability issue I had at my desktop browser width (1280px) was that
opening the picker would hide the document/block sidebarSidebar A sidebar in
WordPress is referred to a widget-ready area used by WordPress themes to display
information that is not a part of the main content. It is not always a vertical
column on the side. It can be a horizontal rectangle below or above the content
area, footer, header, or any where in the theme., but after insertion or otherwise
closing the picker said other sidebar would not return. I would expect it to
do so.
* The outline/list view was very confusing to me because it would change what
levels it was displaying based on whether the cursor focus was inside a widget
area (not always discernible) and because it didn’t expand a collapsed widget
area after selecting a widget inside of it. The latter became VERY jarring
when I then went to insert a widget and it suddenly expanded the area and inserted
the widget there – I had no idea that’s where the insertion point was going
to be.
* Embeds not working is sad. I left a comment on the GitHubGitHub GitHub is a
website that offers online implementation of git repositories that can easily
be shared, copied and modified by other developers. Public repositories are
free to host, private repositories require a paid subscription. GitHub introduced
the concept of the ‘pull request’ where code changes done in branches by contributors
can be reviewed and discussed before being merged by the repository owner.
[https://github.com/](https://github.com/) issue about it.
* The nav menu block is kind of confusing – adding/removing items is pretty slick
but removing them later is kind of scary because it’s not clear whether you’re
deleting one item as a block or the entire menu as a block (it’s the former).
Maybe some highlighting would help here. It’s also a little strange in the
customizer because it shows the contents of the nav menu as links that actually
work instead of no-op-ing.
* Switching to HTMLHTML HyperText Markup Language. The semantic scripting language
primarily used for outputting content in web browsers. editing when there are
legacy widgets shows nothing, and switching back causes the legacy widgets
to lose their entire inner contents so they cannot be edited.
64. And finally, as a data point for what happens with existing widgets, I have a
very old widget I made a long time ago (~2010, has not been touched at all since
2017) which works actually surprisingly well on the insert/edit/preview front,
but blocks saving with the error `There was an error. can't access property "id",
g is undefined` (with the PR for using the new widget endpoints applied). If anybody
wants to use it for testing, it’s here: [https://github.com/helen/really-simple-gallery-widget](https://github.com/helen/really-simple-gallery-widget)
65. * 
* [Yvette Sonneveld](https://profiles.wordpress.org/yvettesonneveld/) 12:32
pm _on_ October 17, 2020
* Sometimes widgets are not visible. Not sure if this is due to the fact that
the theme does not support widgets in that section, but it may be confusing
for average users. Showing in a video here: [https://youtu.be/ilf0sqNBhqk](https://youtu.be/ilf0sqNBhqk)
* 
* [Daisy Olsen](https://profiles.wordpress.org/daisyo/) 9:36 pm _on_ October
19, 2020
* Thanks so much for posting these findings! I’ve captured this feedback and
passed it along for further processing. Some items were already covered by
previously added issues but I’ve created several more as well.
Comments are closed.
# Post navigation
[← Test scrub for WordPress 5.6](https://make.wordpress.org/core/2020/09/29/test-scrub-for-wordpress-5-6/)
[Navigation Screen Removed from 5.6 Release Features →](https://make.wordpress.org/core/2020/10/01/navigation-screen-removed-from-5-6-release-features/)