Docs: Update iframe editor migration guide for WordPress 7.0/7.1#78401
Conversation
The guide described iframe behavior that no longer matches the planned rollout. Correct the conditions so the post editor is iframed based on blocks present in the content (not all registered blocks), move the "always iframe" target to WordPress 7.1, and condense the 6.9 section. Add the WordPress 7.0 change explaining inserted-block evaluation, and a new section on patching external libraries for iframe compatibility. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The bold labels ended with "**:**:", producing a doubled colon in the rendered output. Drop the redundant trailing colon. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @merijnponzo. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
|
Flaky tests detected in 7715347. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/26156010587
|

Closes #73138
What?
Updates the "Migrating Blocks for iframe Editor Compatibility" guide so it reflects the current iframe rollout plan.
Why?
The guide contained outdated and inaccurate information.
How?
patch-package.Testing Instructions
Use of AI Tools
This PR was authored with the assistance of Claude (Claude Code). All content was reviewed by the contributor.