Repository navigation
Conversation
🤖 PR meta 🤖🎉 PropsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Updated as activity occurs, without notifying anyone named here. Add the 📦 Bundle sizeSize Change: +68.2 kB (+0.83%) Total Size: 8.3 MB 📦 View Changed
⚡ PerformanceShow the resultsClient side metrics exclude the server response time. front-end-block-theme
front-end-classic-theme
media-processing
media-upload
post-editor
site-editor
🏁 Flaky testsSome tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information. should cut and paste individual blocks with collapsed selection in
|
33dd3a2 to
822d991
Compare
|
I guess this one should use the toolbar variant to maintain that appearance? |
Yeah I forgot to pre-address that part.
Alternatively, if we're strongly convinced that we will continue to need / use that different visual treatment, we can implement it to |
|
I knew this question would come up at one point. Notably the ellipsis menu for block toolbars will substantially benefit from flyouts. I was hoping it would look okay, but honestly this discrepancy looks like a bug. What are our options for supplying a light reskin of dropdowns just for block toolbar menus? |
|
I considered keeping the overrides in shared block-editor wrappers, but these menus live in several packages. That would mean adding wrapper APIs that other packages need to import and maintain across versions. Adding a visual For the name, @WordPress/gutenberg-components , @WordPress/gutenberg-design and @Mamaduka , WDYT ? |
|
I like "high contrast", but I'll defer to Jay if he has opinions. |
|
Adding the "high contrast" variant to Menu and Popover in #83850 |
|
No decision has been made yet, but there is a proposal to remove the heavy border from the block toolbar. See #67426. I'm concerned that the new variant might become redundant if we decide to make the block toolbar borderless in the future. |
|
Sounds like we should make that call sooner rather than later 😅 |
|
Should we try the I tried vibe coding an unstyled block toolbar. What do you think? Conversely, if the unstyled block toolbar is not well received, it means we will continue to keep the high-contrast look for the block toolbar, which might allow us to move forward with #83850. https://playground.wordpress.net/?gutenberg-pr=84022
|
|
Thank you @t-hamano , I believe @WordPress/gutenberg-design folks plan to take a look at the whole toolbar design situation soon, I expect them to provide feedback in the upcoming week(s) |

Part of #61094.
What?
Use
@wordpress/uiMenu for Move to widget area in both widget editors.Why?
One shared migration updates the Widgets screen and Customizer.
How?
Keep the public props and toolbar integration. Preserve area descriptions, the selected area, and the no-op behavior when selecting the current area. Add the package's direct UI dependency. Exclude menu focus guards from toolbar control detection, and keep Customizer selection when interacting with UI overlays.
Testing Instructions
With a classic theme that has two widget areas, add a Paragraph to the first area. Open Move to widget area in its toolbar and choose the second area. Verify the paragraph moves. Repeat in the Customizer. Selecting the current area should leave the widget and menu in place.
Testing Instructions for Keyboard
Focus the move trigger through the block toolbar. Open it with Enter, navigate with arrow keys, and select a destination. Escape should close the menu and return focus to its toolbar trigger.
Screenshots
Use of AI Tools
Implemented and verified with OpenAI Codex.