-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Try an explicit contentRole for containers where blocks can be added in contentOnly mode #75812
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
base: trunk
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -163,7 +163,8 @@ | |
| "interactivity": { | ||
| "clientNavigation": true | ||
| }, | ||
| "listView": true | ||
| "listView": true, | ||
| "contentRole": true | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Trying to use my meat brain to test today 😄 So I understand, adding the contentRole` prop preserves current behavior for these blocks? I mean, is it saying "this block’s inner area is a content container", and therefore lets users insert allowed blocks (Image) into that area in
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes! |
||
| }, | ||
| "editorStyle": "wp-block-gallery-editor", | ||
| "style": "wp-block-gallery" | ||
|
|
||
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.
Is this still the case? e.g.,
The container is the section root, or...