-
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
Remove use of contentOnly
block editing mode for synced patterns
#67364
Conversation
Size Change: 0 B Total Size: 1.82 MB ℹ️ View Unchanged
|
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. |
I'll YOLO merge this so that the broken e2e tests in trunk are not blocking anyone, but I still encourage peer review/testing/feedback. |
…67364) * Remove use of `contentOnly` block editing mode for synced patterns * Update unit tests ---- Co-authored-by: talldan <[email protected]>
What?
Fixes the broken e2e tests in
trunk
.Removes the use of
contentOnly
mode for the synced pattern block.Why?
contentOnly
mode removes some of the options from the block:It results in the block no longer being groupable, which caused an e2e test failure.
How?
The block now uses the default mode.
Testing Instructions
Also worth testing when the block is used as a section in Write Mode - the settings menu should have a reduced set of sections like any other section.
Screenshots or screencast
Before
After