WordPress 7.1 Breaks Your Blocks: Migrate to iframe Now

WordPress 7.1 ships August 19, 2026, and it closes the escape hatch block developers have been quietly relying on. Since WordPress 7.0, the post editor only ran inside an iframe if every block inserted on the page declared Block API v3 or higher. One legacy block in the mix and the whole editor stayed un-iframed. That protection disappears in 7.1. Every post editor canvas will now run inside an iframe regardless of which blocks are present — full stop. RC1 drops August 5. Seventeen days to fix your blocks.

WordPress 7.1: Five Things That Will Silently Break

The iframe isolates the canvas document from the WordPress admin page. That isolation is the point — viewport units and media queries now measure the canvas, not the browser window — but it also means code that assumed shared context now fails without an obvious error.

The most common breakage patterns: global window references read the wrong viewport, document-level event listeners fire against the admin document rather than the canvas, editor styles loaded via enqueue_block_editor_assets land outside the iframe entirely, CSS selectors targeting .wp-admin or #wpadminbar match nothing in the canvas document, and third-party DOM libraries that call document.querySelectorAll() find nothing. According to the Gutenberg Times migration guide, these failures are silent — no crash, just broken resize handlers and invisible UI elements that users will report long after the update ships.

The fix for window references is to reach through the element to the correct document view:

// Breaks in WordPress 7.1
window.addEventListener('resize', handler);

// Works in WordPress 7.1
const ref = useRefEffect((element) => {
  const { defaultView } = element.ownerDocument;
  defaultView.addEventListener('resize', handler);
  return () => defaultView.removeEventListener('resize', handler);
}, []);

For editor styles, the fix is moving the declaration out of PHP and into block.json. The enqueue_block_editor_assets hook loads assets into the admin page, not into the iframe. Declare "editorStyle": "file:./editor.css" in your block manifest and WordPress will load it inside the canvas correctly.

Block API v3 Migration: One Line, Not One Step

Setting "apiVersion": 3 in block.json is the declaration that signals iframe readiness. Core blocks made this move in WordPress 6.3 — three major releases ago. If you’re still on v1 or v2, that change is overdue. However, the declaration itself is the easy part. The WordPress Developer Blog’s July 2026 roundup is clear: setting apiVersion does not automatically fix your block. It changes what the editor does with it. The audit of your edit component for every document.* and window.* call is still your responsibility.

Run a search for document\. and window\. across your block source. Each match is a potential breakage point. Replace with element.ownerDocument equivalents using useRefEffect. Test against WordPress 7.1 Beta 1 or Gutenberg plugin 22.6 or later — both enforce the iframe in the post editor today.

{
  "apiVersion": 3,
  "name": "my-plugin/my-block",
  "editorStyle": "file:./editor.css"
}

Related: ESLint v9 Dies August 6 — Migrate to v10 Before Your CI Breaks

Three More Breaking Changes in the Same Release

WordPress 7.1 ships the iframe enforcement alongside a coordinated deprecation wave across @wordpress/components. Roughly 20 components — including TextControl, BoxControl, BorderControl, FontSizePicker, RangeControl, ComboboxControl, and ToggleGroupControl — hard-deprecate the __next40pxDefaultSize prop. The 40px control size is now the permanent default. Passing the prop logs a warning and does nothing. Search your codebase for __next40pxDefaultSize and remove every instance.

All 330 icons in @wordpress/icons v15 now declare fill="currentColor". If you styled icons using CSS fill properties, those styles now apply — which may change colors unexpectedly. Switch to CSS color for icon tinting instead of fill. Additionally, the @wordpress/reusable-blocks package is fully deprecated. Every action, selector, and component in it now logs a warning. The migration path is core block patterns.

Three migration tasks in one release is not normal. WordPress 7.1 is not the quiet point release the version number implies.

React 19: Test Now While It’s Still Optional

React 19 is not mandatory in 7.1, but Gutenberg 23.4 introduced an experimental gutenberg-react-19 flag. Enable it in staging and watch the console. Deprecation warnings fire immediately when plugins hit removed React legacy internals. If you use @wordpress/element or compile JSX for blocks, this is the window to catch issues before the upgrade becomes mandatory. The WordPress 7.1 release schedule confirms React 19 is deferred to a later release, but the warnings are live now. Check the full WordPress 7.1 feature overview for what else made the cut.

Key Takeaways

• WordPress 7.1 (August 19) enforces the post editor iframe unconditionally — the Block API v2 escape hatch is permanently gone
• Set "apiVersion": 3 in block.json, then audit all edit component code for document.* and window.* calls — the declaration alone does not fix breakage
• Move editor styles from enqueue_block_editor_assets to the "editorStyle" field in block.json so styles load inside the canvas
• Remove all __next40pxDefaultSize props from components usage; switch icon styling from CSS fill to color
• Enable the gutenberg-react-19 experimental flag in staging now to surface React 19 warnings before they become mandatory