-
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
Block Bindings: Use role content to enable block bindings attributes/ #67745
base: trunk
Are you sure you want to change the base?
Conversation
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. |
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
15d12c0
to
b3e3df5
Compare
Setting as a draft, as last revert introduced some changes on allowed block bindings I need to update. |
Size Change: +27 B (0%) Total Size: 1.83 MB
ℹ️ View Unchanged
|
What?
This is a first iteration of adding "role: content" as an opt-in for block bindings. I still left the
BLOCK_BINDINGS_ALLOWED_BLOCKS
variable, to ensure only blocks that are updated with the required code to process the bindings on the server are included.Tests
E2E tests should pass. This PR is not changing anything yet, just adding another check.