July 22, 2026 — Gutenberg 23.6 shipped July 22 with three threads that shift the editor from plumbing to product: two long-experimental blocks — Tabs and Playlist — finally stabilized, notes learned to anchor to a phrase and route through @mentions, and the Post Editor moved permanently inside an iframe to match the Site Editor. Where 23.5 was about seeing a layout at every width, this release is about what publishers can now stop building themselves — and one architectural change they’ll need to test against before they update.
Key Themes
- Tabs and Playlist blocks stabilized out of experimental status, giving publishers structured tabbed content and an audio player without a plugin or a custom build.
- Notes can now anchor to a specific text selection and carry @mention autocomplete, turning block-level comments into a real editorial-review layer.
- The Post Editor always renders inside an iframe now, like the Site Editor — a convergence that closes a rendering gap and demands a compatibility check for custom meta boxes and editor plugins.
- A new icon registration API lets themes and plugins publish custom icon collections site-wide, and Apply Globally can now push a single property instead of a whole style.
- Responsive styles matured — tablet and mobile preview widths are configurable in
theme.json, text alignment varies per viewport, and the feature was renamed from Responsive editing to Responsive styles.
Jump to: 🧩 Tabs and Playlist Graduate · 📝 Notes Go Inline · 🖼️ The Mandatory Iframe · 🎨 Icons and Selective Styles · 📐 Responsive Styles Grows Up · 🔧 Smaller Updates · 💡 Takeaways
🧩 Tabs and Playlist Graduate
Two blocks that have sat in the experimental tray for releases finally shipped as stable. The Tabs block (#80163) implements the W3C ARIA Authoring Practices Guide tab pattern, supports color, typography, border, and spacing controls on the tab buttons, and adds RichText handlers for editing tab labels in place (#79583) plus toolbar buttons for reordering (#80107) and an aria-label on the tab list (#79948). The Playlist block (#80203) is a full audio track player — metadata, artwork, an optional waveform, and a configurable tracklist with toggles for artist names, track numbers, and length, plus waveform styling (#80065).
Why this matters: This is the build-vs-buy gap closing on two content structures publishers routinely pay for. Tabbed content — spec comparisons, FAQ stacks, multi-section explainers, buyer’s-guide layouts — is exactly what a newsroom either licenses a plugin for or hands to a developer to build as a custom block. A stable core Tabs block with WCAG-grade keyboard semantics baked in retires that line item and the accessibility risk that comes with a homegrown version. Playlist does the same for audio: a podcast network or music-coverage desk gets a native player instead of an embed or a third-party widget. Stabilization is the signal that matters — these are now blocks a platform team can standardize on rather than experiments to keep at arm’s length.
📝 Notes Go Inline, and Learn to @Mention
Notes stopped being a whole-block affair. Inline notes (#78218) attach to a specific text selection instead of the entire block, the highlight persists through subsequent editing, and a single block can carry several inline notes sorted by where they appear. Alongside it, @mention autocomplete (#79604) lets an editor type @ to pull up a keyboard-navigable user list; the resulting mention chip links to the user’s author page and carries their ID. The surrounding polish landed too — a Resolved divider above closed notes (#80019), placeholders in the note fields (#80296), and an Escape-key fix so dismissing the note form no longer cancels the autocompleter (#80224).
Why this matters: The collaboration arc has been about earning trust before adding power — 23.3 and 23.4 were maintenance, and 23.5 added the per-post-type kill switch that let compliance-minded publishers turn co-editing off where it doesn’t belong. 23.6 is the payoff: the review workflow a copy desk actually uses. A margin comment anchored to a single phrase — not a whole paragraph block — is the difference between “fix this sentence” and “something in this block is wrong.” The @mention routes that query to the right editor by name. For newsrooms that fled to Google Docs for the editing pass, this narrows the reason to leave the editor at all — the review layer is now inside the tool where the work ships.
🖼️ The Post Editor Commits to the Iframe
The Post Editor now always renders inside an iframe, aligning it with how the Site Editor has worked for years (#74042). The admin and super-admin bar are also shown by default in both editors now (#79197).
Why this matters: 23.4 was the release we called the Admin’s Visual Convergence — the point where Post and Site editors started to look like one product. This is the structural version of that convergence, and it cuts both ways. The upside is real: an iframe isolates editor content from admin CSS, so the styles a writer sees in the canvas finally match the theme instead of inheriting stray wp-admin rules. The cost is a compatibility audit. Anything that assumed the editor lived in the same document as the admin page — custom meta boxes that reach into the DOM, workflow plugins that inject scripts, homegrown jQuery hooks bound to editor elements — now runs across an iframe boundary. Classic meta boxes get a compatibility shim, but bespoke editorial tooling built by a large publisher’s own team is exactly the code most likely to have queried the editor document directly. Test it in the iframed Post Editor before the plugin update, not after.
🎨 A Registry for Icons, and Styles You Apply One at a Time
- A new icon registration API (#77260) lets themes and plugins register custom icon sets organized by collection, available site-wide in both the editor and the frontend. The icon picker gained a Collections tab for browsing and searching a specific set (#79681, #78332) with async loading, a REST endpoint for collections (#79686), and SVG content sanitized and stored on registration (#80508).
- Apply Globally became selective (#79839): a block’s style can now be pushed to every instance one property at a time instead of applying the whole treatment at once.
Why this matters: Both are design-system governance levers. A registered icon collection turns a brand’s icon library into a governed asset that lives in core — one source of truth instead of SVGs pasted into templates that drift apart over time, with sanitization handled at registration rather than trusted per paste. Selective Apply Globally is the counterpart on the styles side: a design lead can correct a single value — a border radius, an accent color — across every instance of a block without dragging along every other local override that happened to be set at the same time. For a team governing dozens of templates, that precision is the difference between a safe global fix and an accidental cascade.
📐 Responsive Styles Grows Up
- Tablet and mobile preview widths are now configurable in
theme.json(#79104) so the presets match a theme’s real breakpoints instead of Gutenberg’s generic defaults. - Text alignment can vary per viewport state (#80037), the feature was renamed from Responsive editing to Responsive styles (#80241), and the device icon now colors when responsive styles are active (#80346), with inherited Global Styles values reflected in the inspector (#80481).
Why this matters: The responsive arc has been running since 23.2 keyed styles to the viewport, 23.3 made them per-block, and 23.5 shipped the resizable canvas to preview them. 23.6 closes the last honesty gap: the preview breakpoints can now be set to the theme’s actual tablet and mobile widths in theme.json, so what a designer sees when they drag the canvas matches what the front end does — not an approximation. The rename from editing to styles is the tell that the feature is stabilizing out of experiment framing. One more property that varies by viewport, text alignment, means one more thing a newsroom keeps inside the design system instead of handing to a developer’s stylesheet.
🔧 Smaller Updates
A dynamic Gallery variation arrived. A new Gallery block variation (#78796) displays all media attached to a post automatically, in both the editor and the frontend, and switches between dynamic and manual modes without losing settings — useful for photo-desk templates where the image set changes per story.
Background gradients spread across blocks. Gradient backgrounds were added to Accordion (#79840), Post Content (#79842), Pullquote (#79841), Quote (#79843), and Verse (#79391).
Animated GIFs can convert to video. An opt-in transform converts animated GIFs to video via mediabunny (#78410, #80072) — a page-weight win for GIF-heavy posts.
The 40px control-size defaults were hard-deprecated. InputControl (#79962), RangeControl (#79590), and SelectControl (#79797) among others removed their legacy default sizing — a components cleanup that can shift the layout of custom plugin UI built on those primitives.
Performance and accessibility. The Query Loop no longer duplicates block-support CSS (#78282), Latest Posts category selection is optimized for large lists (#80198), text inside a closed Accordion panel is now findable via browser search (#74744), and contrast checking extended to viewport and pseudo states (#80223).
The floor holds at WordPress 6.9. Gutenberg 23.6 keeps the WordPress 6.9 minimum introduced in 23.5 — confirm production is there before updating. The release credits 67 contributors, 7 of them first-timers.
💡 Takeaways
- Evaluate Tabs and Playlist against your custom builds. Test whether the stabilized core blocks can retire a tabbed-content plugin or a bespoke audio player — and the accessibility maintenance that came with them.
- Pilot inline notes with your copy desk. Run text-anchored notes and @mentions through a live review pass and decide whether the editing round-trip through external docs can finally move in-editor.
- Audit editor customizations against the mandatory iframe. Inventory custom meta boxes, workflow plugins, and homegrown editor JS, and test each one in the iframed Post Editor before you update the plugin.
- Register your brand icons as a collection. Hand your design system a governed icon set with sanitization at registration instead of SVGs scattered across templates.
- Align your theme.json breakpoints with the canvas. Set your real tablet and mobile widths so the resizable-canvas preview matches the front end before relying on it for responsive review.
The full changelog is available on Make WordPress Core.