Jb Audras 12:48 pm on August 7, 2025
Tags: 6-9 ( 11 ), canonical plugins, core ( 655 ), dev chat ( 839 ), gutenberg, summary ( 947 )

Summary, Dev Chat, August 6, 2025

Start of the meeting in 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/., facilitated by @audrasjb. 🔗 Agenda post.

Announcements 📢

WordPress 6.9 Roadmap

The roadmap for 6.9 has been published. Please take a look to see what’s actively being worked on for release later in the year.

WordPress 6.9 Planning Proposal and Call for Volunteers

The planning phase for 6.9 wrapped up on July 25. More information will be announced about the release team in the coming weeks.

Maintenance releases for WP 4.7 to 6.7

A maintenance update was released for branches 4.7 to 6.7.

Forthcoming releases 🚀

WordPress 6.9

WordPress 6.9 is scheduled for Tuesday, December 2, 2025. The planning phase wrapped up on July 25. More information will be announced about the release team in the coming weeks.

Discussion 💬

“New blocks in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” guidelines (and their lack of)

Pointed out by @mamaduka: “Do niche blocks belong in the core?”. See the related issue on Gutenberg GitHub repository.

Full discussion on Slack

Read the discussion highlights

@audrasjb suggested that shipping Canonical Plugins are probably a better option for most of the blocks listed in the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue. @desrosj shared the same opinion: “For a while, the use of 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. plugins was encouraged. It would be great to have canonical plugins for blocks that are somehow differentiated in the UIUI User interface to the user as coming from w.org and can be trusted.”

On another side, @richtabor pointed out that Core should propose a more complete set of blocks to meet more user needs: “Blocks (of all kinds) are foundational to the site-building experience—they’re not just extra features, but the literal building blocks of themes and patterns. When a block is missing, it breaks the visual integrity of a theme or pattern, or simply make certain designs impossible. That’s a much more fundamental gap.” […] “I just see hundreds of people asking daily for things that aren’t there, quickly getting lost in the complexity of WordPress (install this. activate that. canonical that).”

@jorbin answered that needing to install things is an expectation from the WordPress project philosophy:

Different people have different needs, and having the sheer number of quality WordPress plugins and themes allows users to customize their installations to their taste. That should allow all users to find the remaining 20% and make all WordPress features those they appreciate and use.
https://wordpress.org/about/philosophy/

@joedolson: “With at least one – the Playlist block – I feel it should be included on the grounds that it’s currently classic functionality missing from the block editor. But overall, I think ubiquity is one of the most major relevant issues.”

@audrasjb and @karmatosed added that having dedicated working groups for each Canonical Block project may be a nice contribution experience for people wanting to contribute to smaller projects than 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/ or Core.

@johnparris: “Instead of bundling more blocks in core, could we improve the user experience for when a block is missing and make it easy to find/install right instead of showing an error? There’s more nuance of course but just thinking in general.”

@joedolson: “an element of where the boundary sits is “is this functionality or design” – fundamental design elements feel appropriate to core, for me. E.g., tabs/accordions/menus/breacrumbs, etc.”

@audrasjb: “We can also just question ourselves why it is not a feature already present in Core. For example, if we don’t have any function to manage breadcrumb trails in Core, then the block is probably 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 territory as well?”

@richtabor: “It’s not about what we want to include in core — I’d say thats the backwards approach. It should be able what people expect when building a site or page. If it’s expected, we should cover it.”

@dmsnell: “I lean on being a bit generous with thinking about additional Core blocks as long as they are generic in nature and existing web idioms. MathML is a good example where it’s definitely a minority need, but one which has been present in the web since the beginning. Blocks like the details block were delayed by two years over discussions about what it should be when again it was in the web platform and a standard idiom.” […] “I find that case-by-case basis for discussion is appropriate, while personally I like leaning on justifying why something shouldn’t be in Core rather than justifying why it should. The canonical plugins seems like a nice compromise to me.”

@audrasjb: “Once a block is introduced, it’s really hard to remove or deprecate, so maintenance / backward compatibility is an important point.” @joedolson completed: “that’s why we need to be very sure that any block we ship is using an optimal pattern.”

@richtabor: “If it’s a slider, you wouldn’t start by inserting a gallery to make a slider. You should be able to convert a gallery into a slider (via block transforms), but that’s not what most users would expect or do. Definitely a delicate balance.”

@jorbin advocated for Canonical plugins: “One of the benefits of getting these into a canonical state (ignoring the question of if they should ship with core for a second) is that core can be responsible for both backcompat and forwardcompat. When the 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 needs to be updated, this also will provide good examples for the community and make it easier to get more sites using the most modern version.”

The discussion ended on some consensus on adding more blocks – in Core or in Canonical plugins – but what is needed is guidelines for how to make the decision on which blocks. A proposal on Make Core may also be a good way to gather more feedback eventually.

Request for comments on a new HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API system for processing blocks

@dmsnell proposed to discuss this PR proposal.

Full discussion on Slack

Read the discussion highlights

This PR provides a Block_Scanner class which allows to walk through the structure of a text with blocks and do interesting things along the way. For example, add CSSCSS Cascading Style Sheets. class names to the “wrapping element” of a block or its inner blocks.

@dmsnell wanted to request feedback on the interface: “There are a couple of new ideas he has taken from expressed pains with parse_blocks(), one being is_non_whitespace_freeform() which sounds like a mouthful, but makes it easy to detect the difference between HTML soup and the newlines that Gutenberg stores between blocks.”

@audrasjb: “I understand the need to have a more robust method than parse_blocks() but I feel concerned about having two things to handle very similar tasks.”

@dmsnell: “I hear you. this started long ago with an attempt to make parse_blocks() lazy but then I ran into problems specifically with nested attribute access in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher. for a reason I still don’t understand, with ArrayAccess things would be broken if you did something like $block['attrs']['settings']['supportsTheme'] = true and it hadn’t yet parsed the 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..” […] “that’s good feedback though, and I think I can do more to help clarify in the docs which is which, including adding a reference in the docs for parse_blocks().”

@jorbin: “Is this parser fully backwards compatible with parse_blocks?”

@dmsnell: “it doesn’t produce the block tree by default, but I did add in the ability to create a sub-block-tree compatible with parse_blocks(). specifically, if you want, for example, to find a gallery block and mess with it, you can scan to the gallery block, then tell the parser to produce the block tree which includes and falls inside the gallery. That lets you mix workflows because a lot of code wants to operate on inner blocks and what not, but a lot of code also only incidentally does that because we don’t have a way to express edits that are simpler.”

@justlevine: “Does this do anything to decouple parsing from rendering, or is it still intended to be hard tied into the rendering output lifecycle?”

@dmsnell: “there was a change I merged some weeks ago to optimize do_blocks() that basically frees up memory after rendering a block. Block_Scanner can technically go further and only parse one top-level block at a time, freeing up more memory. I haven’t benchmarked it, and I doubt it will be faster, but that was the underlying insight which led to the much easier patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. that was merged. This is not intended to replace do_blocks() or render_block(), and parsing has always been decoupled from rendering. It’s viable that do_blocks() could eventually use this, but not necessary and not even the most-valuable place it can be used. Its value mostly appears when wanting to operate on parts of a document or when working with the HTML of a block. for example, I believe this is going to be the mechanism we use when parsing a block’s sourced-attributes on the server for things like block bindings or short-blocks/bits/shortcodes2.0.” […] e.g. “Replace all image block url attributes” as a render-time filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output..

#6-9, #canonical-plugins, #core, #dev-chat, #gutenberg, #summary

Aki Hamano 11:45 am on July 30, 2025
Tags: block-editor ( 120 ), core-editor ( 731 ), gutenberg, gutenberg-new ( 192 )

What’s new in Gutenberg 21.3? (30 July)

“What’s new in 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/…” posts (labeled with the #gutenberg-new 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.)) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.

What’s New In
Gutenberg 21.3?

Gutenberg 21.3 has been released and is available for download!

This release focuses on improvements to the DataViews and other components, as well as inspector sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. enhancements. Below is a curated summary of the most notable changes in this release.

DataViews enhancements

The grid layout of DataViews now supports grouping items by fields. This allows developers to organize large amounts of data efficiently and will be extended to other layouts, such as table layout, in the future.

Furthermore, in addition to the existing datetime field type, DataViews now supports the date field type, which is just a date without a time. This is also needed for filtering dates using the new Calendar component. Filtering and editing features will be implemented in the future.

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. Library Enhancements

The Cover block supports the poster image, so users with a large video file or slow internet connections can see the poster image before the video loads.

The Post Content block supports a tagName selector, allowing you to change the default div wrapper to a more semantic alternative (main, section, article).

MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. to TypeScript continues

An effort is underway to gradually migrate packages to TypeScript. In this release, many packages have been migrated to TypeScript, making them safer and more robust. See #67691 for more details.

Continue reading →

#block-editor, #core-editor, #gutenberg

Héctor Prieto 3:38 pm on July 18, 2025
Tags: block-editor ( 120 ), core-editor ( 731 ), gutenberg, gutenberg-new ( 192 )

What’s new in Gutenberg 21.2? (16 July)

What’s New In
Gutenberg 21.2?

Gutenberg 21.2 has been released and is available for download!

This release focuses on improvements to the DataViews and other components, as well as inspector sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. enhancements. Below is a curated summary of the most notable changes in this release.

Opening links in a new tab gets easier

A small but handy change, the Navigation Link 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. now provides a toggle in the inspector sidebar to open the link in a new tab, bringing it together with the rest of the link options.

DataViews and new components

Gutenberg 21.2 introduces numerous DataViews enhancements and new features. For starters, there are new media, boolean, email, and array field type definitions. Moreover, field type definitions can define a default sorting and rendering function.

You can even break down the DataViews themselves and make different compositions, as the DataViews component now exports its subcomponents independently. There are many new features and some breaking changes; for a comprehensive list, please refer to the full list of changes.

Aside from DataViews, this release introduces the DateCalendar and DateRangeCalendar components as well.

ToolsPanel refactoring continues

Similarly to recent releases, more blocks have had their settings panels updated to a newer UIUI User interface. This time, it’s the turn for the Gallery block, and wrapping up the efforts from the last release, the remaining options of the Site Logo block.

Continue reading →

#block-editor, #core-editor, #gutenberg

Daniel Richards 9:06 am on July 2, 2025
Tags: block-editor ( 120 ), core-editor ( 731 ), gutenberg, gutenberg-new ( 192 )

What’s new in Gutenberg 21.1? (2nd July)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Site Editor project (formerly called Full Site Editing).

What’s New In
Gutenberg 21.1?

Gutenberg 21.1 has been released and is available for download!

This release contains improvements to the Interactivity 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., refinements to 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. tools, and more extensibility features. Below is a curated summary of the most notable changes in this release.

Social Links: Custom Icon extensibility
ToolsPanel refactoring continues
Changelog

Developers can now add new icons to the Social Links block by registering additional block variations. The pull request description has code examples for anyone interested.

Now you can add links for all your pet’s socials:

ToolsPanel refactoring continues

Similar to the last release, more blocks have had their settings panels updated to a newer UIUI User interface. This includes the Author, AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name., Post Navigation Link and Site Logo blocks.

Changelog

Enhancements

Block Library

Author Block: Refactor Settings panel to use Toolspanel. (67965)
Avatar: Refactor settings panel to use ToolsPanel. (67952)
Comments Pagination: Remove unwanted bottom margin from links. (70360)
Navigation Block: Flip submenu indicator icon on submenu expansion. (70307)
Navigation Block: Rotate submenu indicator icons on submenu expansion. (70442)
Navigation Link: Add dropdownMenuProps and a resetAll function. (70505)
Post Navigation Link: Refactor settings panel to use ToolsPanel. (70276)
Refactor Site Logo “Settings” Panel to Use ToolsPanel. (67972)
[ Experimental Form ]: Add example block previews. (70436)

Interactivity API

iAPI Router: Add support for new router regions with attachTo. (70421)
iAPI Router: Support new styles and script modules on client-side navigation. (70353)
iAPI: Export NavigateOptions and PrefetchOptions types. (70315)
iAPI: Introduce AsyncAction and TypeYield type helpers. (70422)

Extensibility

Social: Allow custom link icons using block variations. (70261)

Bug Fixes

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. data: getHomePage: Do not return object until resolved. (70345)

Block Library

Fix : Calendar block: Colors do not change between global styles and theme.json. (70184)
Form Block: Apply class names correctly in the block editor. (70394)
FormFileUpload: Extend audio accept MIME types for iOSiOS The operating system used on iPhones and iPads. compatibility. (70354)
Image: Fix outdated accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) hint on native component. (70346)
Image: Fixed resetAll to return image resolution to default value. (70398)
Revert “Flip submenu indicator icon on submenu expansion (#70307)”. (70427)
Social Links: Allow icon size to be reset and honor theme.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. styles. (70380)
Video Block: Guard against duplicate tracks. (70295)

Interactivity API

Fix image lightbox issues in new full client-side navigation logic. (70416)
iAPI Router: Fix dynamic imports on new visited pages. (70489)
iAPI: Fix captured errors in withScope generators. (70303)
iAPI: Fix duplicated nested regions. (70302)
iAPI: Fix parsing of comments without siblings. (70304)

Global Styles

Fix: Global styles affect all form elements ( Form Block ). (70392)
Implement uniform headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. layout. (70464)

DataViews

Data forms: Achieve vertical spacing with vertical spacing rather than cell padding. (70435)

Post Editor

Fix: Update post-publish panel to use taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. label instead of hardcoded “Tags”. (70410)

Media

Invalidate entities when new media is uploaded. (70405)

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

Fix: Incorrect style handle in RTL style registration for wp-list-reusable-blocks. (70402)

Data Layer

Add private selector support to resolveSelect and suspendSelect. (52036)

Accessibility

Templates API

Templates: Add back button & fix focus loss when navigating through template creation flow. (70091)

Performance

Block Library

Avatar: Optimize user control query. (70511)

Documentation

Add isPostSavingLocked example to doc block. (70370)
Commands: Add stylesheet requirements to README. (70323)
Create Block: Add documentation for custom block namespace. (70215)
Docs: Fix broken links on Developer.WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. (70473)
Fix some typos. (70419)
Fix typo folder-structure.md. (70375)
block-attributes: Add role attribute explanation. (70361)

Code Quality

Patterns: Delete unused property. (70321)
TypeScript: Converts HtmlEntities Package to TS. (69326)
TypeScript: Migrate deprecated package to TS. (70362)
TypeScript: Migrate is-shallow-equal package to TS. (70407)
iAPI: Fix the changelog to include PR 70296 in 6.25. (70309)

Block Editor

Media List: Use ‘placement’ prop for popover positioning. (70350)
Refactor: URLInputButton component to functional reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. component. (70384)
Warning: Replace popoverProps.position to popoverProps.placement. (70347)

Components

Circular Option Picker: Use ‘placement’ prop for popover positioning. (70359)
FormFileUpload: Remove temporary fix for selecting .heic file in Chromium browsers. (70383)

Post Editor

PostAuthorCombobox: Simplify ‘onFilterValueChange’ debounced callback. (70512)

Interactivity API

iAPI: Minor fixes to the Interactivity and Interactivity Router comments. (70420)

Block Library

Social Link: Use placement prop for popover positioning. (70348)

Tools

Testing

Test: Improve document settings sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. locator. (70331)
Ensure the actual tests environment is used for end-to-end tests. (70280)
Skip falling end-to-end tests. (70460)
end-to-end Tests: Add test case for Link color support. (69141)
end-to-end Tests: Minor code quality improvement in some tests. (70382)

Various

Block Library

Remove screencast.com embed block variation. (70480)

First-time contributors

The following PRs were merged by first-time contributors:

@alejandrogonzalvo: test: Improve document settings sidebar locator. (70331)
@BugReportOnWeb: FormFileUpload: Extend audio accept MIME types for iOS compatibility. (70354)
@iamsandeepdahiya: Fix: Incorrect style handle in RTL style registration for wp-list-reusable-blocks. (70402)
@kushagra-goyal-14: TypeScript: Migrate is-shallow-equal package to TS. (70407)
@NidhiDhandhukiya74: Refactor Site Logo “Settings” Panel to Use ToolsPanel. (67972)
@shrivastavanolo: Navigation Block: Flip submenu indicator icon on submenu expansion. (70307)
@USERSATOSHI: TypeScript: Migrate deprecated package to TS. (70362)
@yashjawale: Image: Fix outdated accessibility hint on native component. (70346)

Contributors

The following contributors merged PRs in this release:

@alejandrogonzalvo @BugReportOnWeb @DAreRodz @dd32 @ellatrix @himanshupathak95 @iamsandeepdahiya @im3dabasia @Infinite-Null @jsnajdr @karthikeya-io @kushagra-goyal-14 @Maikuolan @Mamaduka @Mayank-Tripathi32 @NidhiDhandhukiya74 @peterwilsoncc @ramonjd @Rishit30G @SainathPoojary @SantosGuillamot @shimotmk @shrivastavanolo @t-hamano @talldan @USERSATOSHI @vk17-starlord @Vrishabhsk @westonruter @yashjawale @yogeshbhutkar

Props @ramonopoly, @isabel_brison and @andrewserong for peer review. Props @karmatosed for visual assets.

#block-editor, #core-editor, #gutenberg, #gutenberg-new

Carlos Bravo 2:22 pm on June 11, 2025
Tags: block-editor ( 120 ), core-editor ( 731 ), gutenberg, gutenberg-new ( 192 )

What’s new in Gutenberg 21.0? (11 June)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Site Editor project (formerly called Full Site Editing).

Gutenberg 21.0 has been released and is available for download!

This release continues the ongoing effort to refine the editing experience, improve accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), and streamline 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. customization. Below is a curated summary of the most notable changes in this release.

The HTML Element is now selectable on Button and Separator blocks.
Extensive ToolsPanel Refactoring
Accessibility and usability
Changelog

The HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Element is now selectable on Button and Separator blocks.

Users can now choose between <a> and <button> elements for better accessibility in the Advanced panel of the Button block.

For the Separator block, they can choose between <hr> and <div>.

Extensive ToolsPanel Refactoring

Many block settings panels—including Button, Comment blocks, Embed, File, List, Navigation, Post Title, RSS, and more—have been refactored to use the unified ToolsPanel interface, providing a more consistent and organized editing experience.

Accessibility and usability

Several blocks, including Button, Columns, and Details, received keyboard accessibility improvements and better focus management.

Numerous bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes address issues with block controls, gallery image captions, social link translations, and more, resulting in a smoother editing workflow.