What’s new for developers? (August 2026)
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
WordPress 7.1 is scheduled to release on August 19, with RC1 and RC2 already shipped and the Field Guide published. Key developer-facing changes include: responsive block styles with configurable breakpoints via theme.json (@mobile/@tablet keys), pseudo-state styling (:hover, :focus, :active) for Button and Navigation Link blocks, a public SVG Icon API with wp_register_icon_collection() and wp_get_icon(), and the post editor becoming always-iframed regardless of theme type. The Abilities API gains a full execution lifecycle, custom validation, and discovery pipeline. Design System theming adds CSS custom properties and a ThemeProvider component for admin UI branding. The __next40pxDefaultSize prop is now a no-op (form controls render at 40px unconditionally). React 19 is punted again — WordPress 7.1 stays on React 18.3. WordPress Playground received a new multi-site interface and a programmatic Site Manager API. Two security releases (7.0.2 and 7.0.3) also shipped this cycle.
Questions this post answers
How do I define responsive styles for different viewports in WordPress theme.json?
In WordPress 7.1, responsive styles are defined using @mobile and @tablet keys nested inside block style definitions in theme.json. The block's default style acts as the desktop style. Breakpoints default to 480px for mobile and 782px for tablet, but themes can override them via a top-level settings.viewport property. Values must be non-negative lengths in px, em, or rem. WordPress theme developers tracking responsive layout changes find the full breakpoint spec and migration notes on daily.dev.
What blocks support pseudo-state styling like :hover and :focus in WordPress 7.1 theme.json?
In WordPress 7.1, pseudo-state styling (:hover, :focus, :focus-visible, :active) in theme.json is limited to the Button and Navigation Link blocks. States are defined as nested keys inside the block's style object and can be combined with responsive viewport keys like @mobile. A custom states feature using a - prefix also exists but has no user-facing UI yet. Developers building interactive block themes can follow WordPress 7.1 pseudo-state coverage and related Gutenberg updates on daily.dev.
What broke when the WordPress post editor became always-iframed in 7.1?
The most common breakage when the post editor became always-iframed in WordPress 7.1 is code that references the global document or window to manipulate the editor canvas — those now point to the wrong document. The fix is to get the canvas document via ownerDocument and defaultView on an element inside the iframe, and to use useRefEffect for attaching and cleaning up event listeners on canvas elements. Plugin authors navigating the iframed editor migration can track compatibility issues and fixes as they surface on daily.dev.