Aki Hamano 10:47 am on November 12, 2025
Tags: 6-9 ( 72 ), dev-notes ( 596 ), dev-notes-6-9 ( 23 )

Preparing the Post Editor for Full iframe Integration

As part of an ongoing effort to modernize the editing experience, WordPress is moving toward running the post editor inside an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. This work builds upon the original iframe migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. in the template editor and introduces new compatibility measures in WordPress 6.9, ahead of the full transition planned for WordPress 7.0.

For background, see the original post.

What’s Changing in WordPress 6.9

Starting with WordPress 6.9, several important updates have been introduced to prepare for this change, which will be completed in WordPress 7.0.

Browser console warnings for legacy blocks

To help developers identify legacy blocks, WordPress 6.9 now displays a warning in the browser console when a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. is registered with apiVersion 2 or lower. This serves as an early signal to update existing blocks before the post editor becomes fully iframed in WordPress 7.0.

When a block is registered with apiVersion 2 or lower, the post editor runs in a non-iframe context as before to maintain backward compatibility. Developers are encouraged to migrate their blocks to apiVersion 3 and test them within the iframe-based editor to ensure full compatibility with future WordPress releases.

See #70783 for more details.

block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema now only allows apiVersion: 3

Alongside these compatibility measures, the block.json schema has been updated to only allow apiVersion: 3 for new or updated blocks. Older versions (1 or 2) will no longer pass schema validation.

See #71107 for more details.

Why iframe the Post Editor?

The main goal of iframing the editor is isolation. By loading the editor content within an iframe, styles from the WordPress adminadmin (and super admin) no longer interfere with the editor canvas.

This separation ensures that the editing experience more closely mirrors what users see on the front end.

From a technical perspective, the iframe approach offers several benefits:

Admin styles no longer leak into the editor, eliminating the need to reset admin CSSCSS Cascading Style Sheets..
Viewport-relative units (vw, vh) and media queries now behave naturally within the editor.

The iframed Post Editor will make life easier for block and theme authors by reducing styling conflicts and improving layout accuracy.

Props to @mamaduka for helping review this dev-note.

#6-9, #dev-notes, #dev-notes-6-9

lepardman 11:41 am on November 12, 2025

Does this mean there is a solution to this?
https://github.com/WordPress/gutenberg/issues/17854
https://wordpress.org/support/topic/add-classes-to-the-gutenberg-iframe-editor-canvas-body-tag/
- Aki Hamano 12:51 am on November 14, 2025
  
  Thanks for letting me know about that issue. I’ll check it out.
  - lepardman 8:51 am on November 27, 2025
    
    Any insight on the matter @wildworks
Ipstenu (Mika Epstein) 12:11 am on November 14, 2025

What will happen to older blocks? Will they just break?

There are a lot of people out there with blocks that aren’t going to be updated in time for 6.9 (less than a month) and this could be a massive lift if they’re going to break.

BackCompat in WP is one of it’s hallmarks, and people have enough reasons to be anti-GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, so I really hope a graceful fallback will exist.
- Aki Hamano 12:57 am on November 14, 2025
  
  What will happen to older blocks? Will they just break?
  
  Nothing will change in WordPress 6.9. Blocks will continue to work as before. You will simply receive a browser warning.
  
  Of course, we understand that WordPress values backward compatibility, so we are trying to proceed carefully.
  
  We will also prepare a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guide. See this issue for more details.
  - Ipstenu (Mika Epstein) 5:18 am on November 14, 2025
    
    And in 7.0?
    
    A migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guide is great for active devs, but we all know not all blocks will be updated by 7.0, and not all plugins and themes will get their update out before someone updates 7.0
    
    So. What happens in 7.0? Do the blocks stop showing anything? Is there a plan to inform end users, not the devs, about this possibly breaking change?
    
    Please, remember the drama when we (for security) had to break an undocumented feature of shortcodes. Have someone scan the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party repo for the number hosted on .org that have a high chance of breaking.
    
    If you don’t get ahead of this now, it’s going to be a dumpster fire.
- Ella Van Durpe 3:16 pm on November 17, 2025
  
  Most blocks with version 1 and 2 blocks work fine with the iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.. There’s a small amount that might not, and it’s not as easy as scanning the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party repo for a piece of code. It would involve going through every plugin and testing the blocks they have. At them moment, I don’t know of any blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. that doesn’t work, I would actually love to find one.
  
  Everything is iframed except the post editor in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: block previews, template editor, site editor and device previews are all iframed and have been for years, so if the block is broken, it has usually been noticed over the past years. When both the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ plugin and a block theme are active, the post editor is also iframed to get even more testing.
  
  We might be able to add some backwards compatibility fallback for some cases, but it would be great to have a list of plugins that don’t work to test with.
  - Ella Van Durpe 3:25 pm on November 17, 2025
    
    Not being consistent about the iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. is creating a worse experience for users: the iframe might turn on or off depending on the plugins installed and cause blocks to render very differently and leave users confused. We’re currently “breaking” a lot of blocks visually that are expecting an iframe, but then we sometimes render blocks without an iframe depending on the compatibility of plugins installed.
  - Ipstenu (Mika Epstein) 10:06 pm on November 17, 2025
    
    and it’s not as easy as scanning the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party repo for a piece of code.
    
    That’s kind of terrifying. Do we even have an idea what might break?
    
    Below:
    
    If your blocks have libraries or code that rely on a global document or window, you may run into issues.
    
    So we can’t look for that?
    - Ella Van Durpe 7:53 am on November 18, 2025
      
      Do we even have an idea what might break?
      
      I’m not certain of all the ways things could break, but for example some blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. relying on querying the DOM from the window/document instead of the block element, or a block using a third party library that does something like that. I’ve documented that here: https://make.wordpress.org/core/2021/06/29/blocks-in-an-iframed-template-editor/.
      
      So we can’t look for that?
      
      That would be specifically in the context of a block edit function, and there’s a ton of ways to do that. Sometimes even hidden if the problem is in a library. I can’t think of a good way to search for it. 🤔
    - leemon 8:24 am on November 18, 2025
      
      The non-jQuery version of Masonry shipped in WP is a notoriously example of a script that doesn’t work in the iframed editor.
Aki Hamano 5:56 am on November 14, 2025
What happens in 7.0? Do the blocks stop showing anything?

No. If your blocks have libraries or code that rely on a global document or window, you may run into issues. Other blocks should continue to work as usual. See this post, which was posted over 4 years ago, for an explanation of when migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. is necessary.

Additionally, not that we’re not trying to force iframes on all editor instances all at once in 7.0 — many editors already run as iframes regardless of the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.’s APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. version. For example, the following always works as an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. editor:
- All block editors in the site editor
- Block theme and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party enabled
- Zoom out mode enabled
- Mobile or Tablet Preview
- Pattern or Template editor
- Ipstenu (Mika Epstein) 6:06 pm on November 14, 2025
  
  Four years is along time in dev land and things may have changed, so forgive me for not taking a four year old ticketticket Created for both bug reports and feature development on the bug tracker. as source-of-truth.
  
  I’m concerned with the post editor at the moment, since that’s what most people use, day in and day out.
  
  Now if the answer is “If you’re using non APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. 3.0 blocks, you will not use the iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.” then that should be in the body of your post so it’s crystal clear 🙂
  
  I strongly urge you to do that scan. Figure out how many people would have broken blocks if you switched over today (7.0 will be here before you know it). That will give you an idea how important testing this sort of back-compat is! Also you will need to check with a lot of random blocks, and make sure it properly fails back to non-iframe. If you start by assuming the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. is not v3, and having it be a fall IN and not a fall BACK, you will save yourself a world of hurt.
  
  Also get that migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guide up ASAP and have plugins email everyone with a block. Telling people ‘this will change in the next version’ without that puts extra work and FUD on the thousands of developers out there who maybe don’t watch all the feeds (or missed one). Devs need to be able to trust that WP isn’t going to break a key feature, and you have to get ahead of this.
  
  Remember most developers aren’t from big companies. They don’t have a ton of resources. We have to make this tenable for them, or we lose them.
  - Aki Hamano 12:44 am on November 15, 2025
    
    Thanks for the suggestion. Since I cannot judge and decide on those suggestions on my own, I will link your comment to this issue.
  - Benjamin Zekavica 8:39 am on November 15, 2025
    
    @ipstenu I understand your concerns. Especially smaller companies are still using custom blocks that won’t work with version 3. But at some point, we have to say that older implementations can’t be supported in future major releases.
    
    That’s why I think the decision is correct: show a warning first and give developers time to refactor their blocks. A clear guide or migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. document will definitely be needed, because otherwise there will be a lot of criticism and some backends will break after the 7.0 update.
    
    @wildworks If you want, we can bring this up in the next dev chat and discuss it with the other developers to hear their experiences. Should I add it to the agenda for Wednesday?
    - Aki Hamano 9:10 am on November 15, 2025
      
      > If you want, we can bring this up in the next dev chat and discuss it with the other developers to hear their experiences. Should I add it to the agenda for Wednesday?
      
      Of course, please feel free to bring this up.
      
      By the way, there have been efforts to make the post editor work as an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. multiple times over the past few years, and it’s been discussed on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. However, we’ve reverted those efforts due to feedback from consumers that it wasn’t ready yet.
      
      With this in mind, and to draw more attention to this effort, we’ve published a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and added a browser console warning in the 6.9 cycle.
      
      Here are some past discussions on this topic:
      
      https://wordpress.slack.com/archives/C02QB2JS7/p1675944840224609
      https://wordpress.slack.com/archives/C02QB2JS7/p1746436039651309
    - Ipstenu (Mika Epstein) 11:34 pm on November 16, 2025
      
      I get that, but “at some time” being two major releases of WP, with a BREAKING change is not in alignment with the previous ways in which WordPress has handled depreciation. Ask yourself, how long do we keep other features flagged with doing it wrong, and how long do we support old versions of WP?
      
      The standard has been 3 versions. Cutting it to 2 means if you missed it in 6.9, you’re screwed in 7.0.
      
      Also the alerts being in console make them far too easy for someone to miss. There has to be a better way to notify, and you’ve got to get ahead of it.
      
      Remember, too, when these sites break, the developer will not know unless they see it. The users may not even know what pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party! The console log errors for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ have, historically, been lacking due to the limitations of the console log itself.
      
      I nearly had a site down because I didn’t see the console log, and I didn’t see a clear post about this. And I was working on the plugins team at the time. Believe me, this is easy to miss, and any time you’ve got a break in change, you have to shift your view to “user first.” Even at the cost of progress.
      
      If you break people’s sites and it’s hard for the site owner to fix, they won’t find a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. alternative, they will find a WordPress alternative. Don’t back on the sunk cost fallacy.
cbirdsong 8:50 pm on November 14, 2025

Is there a way to force the editor into an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. to see what will happen to pre-apiVersion 3 blocks?
- Aki Hamano 12:39 am on November 15, 2025
  
  Is there a way to force the editor into an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. to see what will happen to pre-apiVersion 3 blocks?
  
  As I described here, many editors already work as iframes, so you should be able to use them to test how your blocks work.
Timi Wahalahti 9:44 am on November 17, 2025

Voicing some of the same concerns as @ipstenu has above.

Two versions just isn’t enough time for the switch. It’s not affecting only plugins, but it will affect custom built sites by agencies, freelancers and hobbyists.

Many have built interactions between the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor and other parts of the dashboard etc in a way which iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. will break. One very concrete example is the body class @rickiwylder mentioned; altering page color scheme for example based on the body class both on frontend and editor.

There’s no way you will reach all of the agencies, freelancers and hobbyists to tell them about the change. That leads client’s sites breaking, loss of trust to WordPress (and maybe even the professional(s) who built the site) and extra havoc nobody needs.

Nobody needs further loss of trust to WordPress. It’s bad if clients stop trusting us, but it’s even worse if they lose trust to their website partner. It can quickly lead the professionals to look for alternative CMS’es.
- Riad Benguella 7:06 am on November 18, 2025
  
  This is not dissimilar to a jQuery upgrade we made before. We know this is the right thing to do, we’ve known this for 4 years now and we’re trying to iteratively get there with the least disruptions possible. Can we can get there with 0 disruptions? no, it’s impossible, can we try to limit these? Yes, we can and we’ve been iterating towards this for some time already and are likely to continue.
  
  – We’ve introduced blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. v3 and we asked people to upgrade and check failures.
  – We’ve made “previews” work in iframes for 4 years now
  – We’ve made the site editor use iframes from the start
  – We’ve made both post editor and site editor use iframes in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for some time now as well.
  
  By now, most (not all) people should have already seen errors in their plugins. We need to make another step forward. We’re raising more awareness and visibility for folks to upgrade their blocks.
  
  We’re still assessing our next steps. One possibility might be to enable it only for block themes in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  - Ipstenu (Mika Epstein) 4:14 pm on November 19, 2025
    
    We’ve introduced blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. v3 and we asked people to upgrade and check failures.
    
    This here is my point.
    
    There is a monumental difference between “asking” people to upgrade, and giving them a _one version deadline_.
    
    I see an ask, and historically in WP I think “Oh but I have time and it’ll be public deprecated first.”
    
    If you’re giving someone a deadline, which in essence you are with 7.0, then 6.8 was the time to announce “As of 7.0, we WILL be on iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser., here’s how you can test, and here’s what to expect.”
    - Riad Benguella 7:19 am on November 20, 2025
      
      And my point is that we asked people to upgrade 4 years ago already.
    - Riad Benguella 7:30 am on November 20, 2025
      
      I realize my answer is too short and doesn’t fully convey my thoughts.
      
      4 years is enough time for people to upgrade even without timelines, specially since you probably already had a case where your blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. was used in an iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. during that time.
      
      This is the next step in the process, setting a deadline in place and one version doesn’t mean tomorrow. It means you already had 4 years to upgrade, we’re giving you 4/5 more months to do so, which is still enough time.
      - Ipstenu (Mika Epstein) 8:58 pm on November 25, 2025
        
        4 years is enough time if people knew they’d been asked and told “This is why.”
        
        I think the deadline is too soon for the majority. Should they have noticed? Yes. Did WP email developers and public post a timeline so people would be aware of a deadline? Not until this post that I know of. It’s possible I missed a post, but that really underscores how easy it is to miss.
        
        The expected deadline from previous versions, based on how WP has a ‘this version minus 2’ support trend, would be:
        
        v 6.9 – Set the deadline of 7.1
        v 7.0 – Slap as many public warnings as possible
        v 7.1 – iframes ahoy
        
        It feels like someone wanted this for an arbitrary 7.0 as a big number.
The Worst Wordpress Developer Alive 8:01 pm on November 18, 2025

Is there any WordPress hook that lets me add custom classes to the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) inside the iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.?
Bridget Willard 9:23 pm on November 18, 2025

I read “iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.” and I feel ill.

In the 2015-2017 era when I was with GiveWP, we were always promoting our our donation form was so much better because it was embedded natively, not an iframe that didn’t look like it belonged to the website.

In the case of payments (donations) and iframe is always more sketchy than a cart experience that is styled like the website and encourages trust for the site.

I read the comments above about isolating the text, but isn’t the text isolated in the database?

What am I missing here?

Your friend, Bridget
- Matt Cromwell 11:18 am on November 19, 2025
  
  The irony though now, Bridget, is that GiveWP now uses an advanced form of an iFrameiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. for the donation forms now. There are advantages and there are programmatic ways to avoid the pitfalls of old school iframes nowaday too. Jason Adams was really important to help us navigate how to give users customization abilities while also protect the forms from style and js conflicts. That’s the big advantage – isolation from the rest of the environment that might create javascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. conflicts.
- Miguel Fonseca 9:58 am on November 20, 2025
  
  To be clear, the iframing in question only concerns WP’s editors, not the frontend of the site. So rest assured: site visitors won’t be affected. Not to mention that, as Matt explains, these iframes are invisible and very much unlike the frames of yore. 🙂
John Parris 3:27 pm on November 19, 2025

> To help developers identify legacy blocks, WordPress 6.9 now displays a browser warning when a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. is registered with apiVersion 2 or lower.

When I first read this, I thought it meant a user-facing notice that’s visible when entering the editor, but it appears to be only a console message. Could you update the post to make that clearer for people not reading comments or the PR?
- Aki Hamano 9:52 am on November 23, 2025
  
  When I first read this, I thought it meant a user-facing notice that’s visible when entering the editor, but it appears to be only a console message. Could you update the post to make that clearer for people not reading comments or the PR?
  
  Admittedly “browser warning” isn’t accurate. I’ve clarified the explanation to indicate that the message appears in the browser console.

Welcome!

Communication

Preparing the Post Editor for Full iframe Integration

What’s Changing in WordPress 6.9

Browser console warnings for legacy blocks

block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema now only allows apiVersion: 3

Why iframe the Post Editor?

Welcome!

Communication

What’s Changing in WordPress 6.9

Browser console warnings for legacy blocks

block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema now only allows apiVersion: 3

Why iframe the Post Editor?

Share this:

Site resources