-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 Library: Set freeform handler only if Classic block exists #52936
Conversation
Size Change: +518 B (0%) Total Size: 1.44 MB
ℹ️ View Unchanged
|
Thanks again for your effort on this. Using this PR, I'm not able to reproduce the freeform error in both my test case plugin or in my extended plugin (that my test-case is based off of and contains several more blocks) . Upon the gutenberg plugin's activation, I receive the notice Looking at my debug log, it's just the following; which may be fixed in #52935 ? This may be fixed in #52935 ? |
Flaky tests detected in ec67e05. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5666046872
|
What?
This PR updates the block library to set the freeform content handler to the classic block only if the classic block actually exists.
This PR is part of the fix to address #52811.
Why?
With this additional check, the freeform content handler will not be set if the TinyMCE removal experiment is turned on and the Classic block is intentionally not registered.
That way, the empty whitespaces won't be parsed to empty freeform blocks.
How?
We're just specifically setting the freeform content handler to the classic block only if the classic block actually exists.
Testing Instructions
Testing Instructions for Keyboard
None
Screenshots or screencast
None