-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Notes: Add block support note. #72458
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
Conversation
|
Size Change: +38 B (0%) Total Size: 2.2 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 7b85ef4. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/18607482293
|
t-hamano
left a comment
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.
Thanks for the PR!
Personally, I think the note feature should work for all blocks and shouldn't be a part of the block supports. For example, users might want to add a comment like this to a block:
- The block is broken. Please replace it with a different block.
- Convert this classic block to another block.
Technically, the notes feature should work even with broken or classic blocks.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If 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. |
|
Thank you for your review.👍 I also believe it would be better if the notes feature worked across all core blocks.
Is this a bug in the classic or missing blocks? At the moment, the notes feature doesn't work in classic or missing blocks. note.mp4 |
This needs to be looked into first. Furthermore, I found that many features don't work in broken blocks, such as locking, renaming, hiding blocks, and notes. These are bugs, so I think they need to either hide the menus in the first place or fix them to work. As for the Classic block, I overlooked the fact that this block doesn't have HTML comments in the first place. Therefore, the notes feature might need to be disabled in Classic blocks. |
|
I agree. Notes should be available for all blocks. The Freefrom/Classic block is an odd one, meant to be a block before content is migrated. |
|
Block supports are public API which means anyone can disable the feature for a specific block(s). This isn’t how Notes are supposed to work. P.S. Not everyone editor feature needs to have an associated block support flag. |
What?
Add block support note.
Close #72521
Related #54426
Why?
Notes are a very useful feature, but there may be cases where you don't want to add notes to custom blocks.
This maintains consistency with renaming, locking, blockVisibility, etc.
How?
Testing Instructions
note:falseto the supports property of any block'sblock.json.Testing Instructions for Keyboard
Screenshots or screencast
I will add someone who is knowledgeable about Note to the review.