You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched for any related issues and avoided creating a duplicate issue.
Please give us a description of what happened
As of WordPress 6.3, the post editor is finally also getting rendered in an iFrame for non block-based themes if all registered blocks support apiVersion 3 and there are no classic metaboxes registered. (See the Dev Note)
Sadly Yoast still uses this method for integrating into the edit post screen and is therefore blocking us from finally being able to use the iframed post editor.
To Reproduce
Step-by-step reproduction instructions
Install a clean WordPress 6.3 environment
Activate a traditional or hybrid theme (such as twentytwenty)
Open the post editor
See that it is rendered inside an iframe
Activate the Yoast SEO plugin
Open the post editor
See that it isn't rendered in an iframe
Expected results
Even with Yoast SEO enabled, the post editor should be able to render in an iframe
Actual results
The post editor is blocked from rendering in an iframe when Yoast SEO is active
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
I'd also like to point out that this issue has been present in previous WordPress versions also. Just only for block-based themes such as twentytwentyone, twentytwentytwo, and twentytwentythree
Please give us a description of what happened
As of WordPress 6.3, the post editor is finally also getting rendered in an iFrame for non block-based themes if all registered blocks support apiVersion 3 and there are no classic metaboxes registered. (See the Dev Note)
Sadly Yoast still uses this method for integrating into the edit post screen and is therefore blocking us from finally being able to use the iframed post editor.
To Reproduce
Step-by-step reproduction instructions
twentytwenty
)Expected results
Actual results
Screenshots, screen recording, code snippet
If possible, please provide a screenshot, a screen recording or a code snippet which demonstrates the bug.
The code in core controlling whether the editor gets loaded in an iframe is located here: https://github.com/WordPress/gutenberg/blob/trunk/packages/edit-post/src/components/visual-editor/index.js#L357C7-L364C8 As you can see, it checks whether there are any traditional metaboxes rendered in the editor and if so bails out.
Technical info
Used versions
The text was updated successfully, but these errors were encountered: