-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Tweak remove block label to make it simpler #49529
Conversation
Size Change: +4.22 kB (0%) Total Size: 1.37 MB
ℹ️ View Unchanged
|
Flaky tests detected in 1e2e50f. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4630051363
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@richtabor Please see my note below.
packages/block-editor/src/components/block-settings-menu/block-settings-dropdown.js
Show resolved
Hide resolved
Removing the block name makes sense to me. The name is already present in the toolbar, and this menu item becomes unwieldy when dealing with blocks that have a long name (mostly template parts and reusable blocks). Speaking of... do you think there's a risk that 'delete' could be misconstrued when dealing with those blocks? |
I don't think so. The term "Delete" seems more common/standard practice. What do you think may be misunderstood? |
We'll be offering two delete actions for template parts / reusable blocks. One in the management views which permanently deletes from the entire site. And one in the full-screen editor which just removes it from the current document. Hopefully the context will adequately clarify the differences though. |
🚀 |
What?
Simplifies the "Remove {blockName}" menu item within the block settings menu, in support of #49271 (comment)).
Renders "Delete" when one block is selected, and "Delete blocks" when more than one block is selected.
Why?
We don't have, nor need, additional context on any other menu item (nor this one), as it can be quite noisy and harder to scan.
How?
Testing Instructions
Screenshots or screencast
Before:
After: