Experimental: Backend handle freeform blocks with TinyMCE removal

[tyxla]

What?

Handle freeform blocks properly as classic blocks and load the Classic block and TinyMCE properly.

Part of the fix for #52811.

Why?

There are pre-existing posts that specifically have freeform blocks and we need to handle them properly when the TinyMCE experiment is enabled.

How?

In addition to treating a raw block with content and no name as a Classic block, treat core/freeform blocks as such.

Testing Instructions

• Go to Experiments http://localhost:8888/wp-admin/admin.php?page=gutenberg-experiments.
• Enable the "Disable TinyMCE and Classic block" experiment and click "Save Changes".
• Create a post with this HTML:

<!-- wp:freeform -->
<p>test</p>
<!-- /wp:freeform -->

• Save the post.
• Refresh the page.
• Verify you can see the Classic block and it works correctly.

Testing Instructions for Keyboard

None

Screenshots or screencast

None

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ lib/experimental/disable-tinymce.php

[github-actions]

Flaky tests detected in bf7a161.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5666635087
📝 Reported issues:

• [Flaky Test] should toggle "lightbox" in saved attributes #52350 in /test/e2e/specs/editor/blocks/image.spec.js
• [Flaky Test] zoom animation #52381 in /test/e2e/specs/editor/blocks/image.spec.js

[Mamaduka]

Works as expected ✅

[github-actions]

Warning: Type of PR label error

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Accessibility (a11y), [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: [Type] Enhancement, [Package] Block library, [Block] Classic, [Type] Experimental.

Read more about Type labels in Gutenberg.