[Widget Screen] Adding blocks to columns from 'Browse All' does not work as expected #33658
Labels
[Feature] Widgets Customizer
Ability to add and edit blocks in Customize → Widgets.
[Feature] Widgets Screen
The block-based screen that replaced widgets.php.
[Package] Edit Widgets
/packages/edit-widgets
[Type] Bug
An existing feature does not function as intended
Description
When adding a columns block in the widgets editor, adding blocks to the columns from 'browse all' does not behave as expected/how adding blocks to a column works in the regular editor. A block added from 'browse all' does not get added to the intended destination column where + was clicked. Instead it is added below the column block.
Adding blocks from the options presented in the initial block picker does work as expected.
Additionally, the search feature does not work in 'browse all' unless you first search and then clear that search before searching again OR click somewhere outside the search field within 'browse all' to reveal all available blocks before searching.
Step-by-step reproduction instructions
Expected behaviour
I expect that when clicking + in a column and clicking 'browse all' I will see a list of available blocks and can click a block in that area to add it to the destination column where + was clicked.
I expect that searching from 'browse all' will show all blocks that match my search criteria.
Actual behaviour
When clicking + in a column within a column block and then clicking 'browse all', I see only the column block in the 'browse all' area that slides out. I cannot see the available blocks until I click somewhere in the 'browse all' area.
Once available blocks are revealed, clicking a block does not add it to the destination column where + was clicked. Instead, it adds it below the column block as a new independent block.
When clicking search in 'browse all' without having first clicked elsewhere in 'browse all', the search returns no results.
Screenshots or screen recording (optional)
WordPress information
Device information
The text was updated successfully, but these errors were encountered: