--- title: Iframed Editor Changes in WordPress 7.1 | daily.dev description: WordPress 7.1 makes the post editor always iframed, completing a multi-release migration that started with the template editor in WordPress 5.8. Previously,... canonical: https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Iframed Editor Changes in WordPress 7.1 | daily.dev og:description: WordPress 7.1 makes the post editor always iframed, completing a multi-release migration that started with the template editor in WordPress 5.8. Previously,... og:url: https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r og:image: https://api.daily.dev/og/posts/6RVUkoC5r.png og:image:alt: Iframed Editor Changes in WordPress 7.1 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Iframed Editor Changes in WordPress 7.1 **[Make WordPress Core](https://daily.dev/sources/wordpresscore)** · 3 min read · 6 upvotes · 0 comments ## Summary WordPress 7.1 makes the post editor always iframed, completing a multi-release migration that started with the template editor in WordPress 5.8. Previously, whether the post editor used an iframe depended on the block API versions present in the content. Now it is unconditionally iframed regardless of theme type or block API versions. Block developers should test custom blocks in the fully iframed post editor. The most common compatibility issue is code that references the global document or window instead of the iframe's own document — the fix is to use ownerDocument and defaultView from canvas elements, and useRefEffect for event listeners. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does my WordPress custom block break in the post editor after upgrading to WordPress 7.1? WordPress 7.1 makes the post editor always iframed, regardless of theme type or block API versions, so code using the global document or window to reach the editor canvas now targets the wrong context. The iframe has its own separate document and window. Fix it by getting the canvas document via ownerDocument and defaultView from an element inside the canvas, and using useRefEffect for event listeners. _daily.dev helps plugin developers track WordPress editor breaking changes before they hit production._ ### When did WordPress start iframing its editors? WordPress began moving editors into iframes starting with the template editor in WordPress 5.8. The site editor, template editor, and device previews have since been unconditionally iframed, while the post editor remained conditional based on block API versions until WordPress 7.0, and became always iframed in WordPress 7.1. _developers upgrading WordPress core versions can follow editor architecture changes like this on daily.dev._ ### How did WordPress 7.0 decide whether to iframe the post editor? In WordPress 7.0, the post editor was iframed only if every block inserted in the post used block API version 3 or higher; if any lower-version block was present, the iframe was dropped to preserve compatibility. This conditional logic meant the same post editor could switch between iframed and non-iframed modes depending on its content. _teams debugging inconsistent WordPress editor behavior across posts can find changes like this via daily.dev._ ## Similar posts on daily.dev - [Iframed Editor Changes in WordPress 7.0](https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-0-6nfqeddao) · Make WordPress Core · 4 upvotes · 0 comments - [Preparing the Post Editor for Full iframe Integration](https://daily.dev/posts/preparing-the-post-editor-for-full-iframe-integration-7rvfzjlmv) · Make WordPress Core · 1 upvotes · 0 comments - [What’s new for developers? \(February 2026\)](https://daily.dev/posts/what-s-new-for-developers-february-2026--wtaotv4rw) · WordPress Developer · 23 upvotes · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#wordpress](https://daily.dev/tags/wordpress) [View this post on daily.dev](https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Iframed Editor Changes in WordPress 7.1","url":"https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r"},"datePublished":"2026-08-03T06:07:33.590Z","dateModified":"2026-09-13T20:32:37.455Z","description":"WordPress 7.1 makes the post editor always iframed, completing a multi-release migration that started with the template editor in WordPress 5.8. Previously,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6ad4f5b66be737a1618019916626b1bd?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6ad4f5b66be737a1618019916626b1bd?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Make WordPress Core","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Make WordPress Core","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/892d1a79e30e4e8a911b5726c6fb1a06","url":"https://daily.dev/sources/wordpresscore"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,wordpress","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Make WordPress Core","item":"https://daily.dev/sources/wordpresscore"},{"@type":"ListItem","position":3,"name":"Iframed Editor Changes in WordPress 7.1"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/iframed-editor-changes-in-wordpress-7-1-6rvukoc5r#faq","mainEntity":[{"@type":"Question","name":"Why does my WordPress custom block break in the post editor after upgrading to WordPress 7.1?","acceptedAnswer":{"@type":"Answer","text":"WordPress 7.1 makes the post editor always iframed, regardless of theme type or block API versions, so code using the global document or window to reach the editor canvas now targets the wrong context. The iframe has its own separate document and window. Fix it by getting the canvas document via ownerDocument and defaultView from an element inside the canvas, and using useRefEffect for event listeners. daily.dev helps plugin developers track WordPress editor breaking changes before they hit production."}},{"@type":"Question","name":"When did WordPress start iframing its editors?","acceptedAnswer":{"@type":"Answer","text":"WordPress began moving editors into iframes starting with the template editor in WordPress 5.8. The site editor, template editor, and device previews have since been unconditionally iframed, while the post editor remained conditional based on block API versions until WordPress 7.0, and became always iframed in WordPress 7.1. developers upgrading WordPress core versions can follow editor architecture changes like this on daily.dev."}},{"@type":"Question","name":"How did WordPress 7.0 decide whether to iframe the post editor?","acceptedAnswer":{"@type":"Answer","text":"In WordPress 7.0, the post editor was iframed only if every block inserted in the post used block API version 3 or higher; if any lower-version block was present, the iframe was dropped to preserve compatibility. This conditional logic meant the same post editor could switch between iframed and non-iframed modes depending on its content. teams debugging inconsistent WordPress editor behavior across posts can find changes like this via daily.dev."}}]} ```