Disable TinyMCE: Handle old core/freeform syntax in editor#72967
Conversation
youknowriad
left a comment
There was a problem hiding this comment.
LGTM 👍 Thanks for the fix.
|
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. |
|
Size Change: +7 B (0%) Total Size: 2.45 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 77bd89e. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19068565511
|
What?
Fixes handling of the old
core/freeformblock syntax by the missing block logic.Why?
This is part of the experiment to disable TinyMCE loading by default, while still making it load where necessary.
How?
In addition to handling raw code blocks in the editor as freeform blocks, we're now also handling explicit
wp:core/freeformones.You'll also need the fix from #72966, otherwise you'll be getting some errors when attemtping to load a post that has a classic block.
Testing Instructions
core/freeformblock as shown on the video.<div class="notice">You can include <em>raw HTML</em> here.</div>without thecore/freeformwrapper and verify it continues to recognize it as a "Classic" block.Here's the block markup I'm testing with in the video:
Testing Instructions for Keyboard
Same
Screenshots or screencast
Before:
Screen.Recording.2025-11-04.at.14.37.37.mov
After:
Screen.Recording.2025-11-04.at.14.36.40.mov