The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
The full chat log is available beginning here on Slack.
Open Floor
@swissspidyshared a previous question from @spacedmonkey, regarding the use of static variables in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. for in-memory caching, and whether the object caching APIAPIAn 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. with a non-persistent cache group might be a better alternative. Benefits noted included cache invalidation capabilities and improved testing scenarios. In the original discussion thread:
@flixos90 questioned the practical advantages of cache invalidation for non-persistent caches.
@spacedmonkey clarified it would allow developers to optionally enable persistent caching, improve testability by clearing caches between tests, and align with the intended usage of the object cache API.
@flixos90 agreed that while making these caches persistent could introduce issues, improved testing practices were indeed a valid benefit.
@spacedmonkey also requested feedback on PR #8728, inviting further input from contributors.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
The following tickets were mentioned by Will Garcia on Slack. They asked whether these tickets are likely to be fixed, since the related dependencies are frequently pointed out as outdated by security compliance audits:
Concerning #61175 (Integrate PHPStan into the core development workflow): “We still to have a serious look at what PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Static Analysis errors we want to ignore (e.g. bc they conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with WPCSWordPress Community SupportA public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016., should be handled in a follow-up after the tool is merged, etc) vs baselined (enforced on new code, but not justifiable enough on it’s own to the required criteria for a code refactor).” For more info on this topic, see this thread in the #core-coding-standards channel.
Also they pointed out that “there’s some PHPStan Level 0 +1 errors that I need help remediating (if we dont baseline/ignore them in the previous bullet) […] If anyone else is interested in lending a hand here, please chime in on the ticket, in chat, or via DM”.
@sirlouenmentioned: as per Monday’s bugbugA 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. scrub there are two tickets that need to discussed about errors in Direct Execution of Files. See tickets #62722 and #63316. The discussion should go around if this kind of issues should be covered or is not something of priority for WP.
Finally, @krupajnanda proposed the following: “I’d love to discuss some pointers shared in the recent WCEU Core Committers notes, especially around improving the quality and timing of testing, reviving structured user testing, and making better use of tools like the betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.pluginPluginA 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. Looking forward to some guidance and input on how test team can align better with the Core team’s needs.”
Open floor 🎙️
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.
Since WordPress 6.8 on April 2025, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.orgThe 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/ Support Forums, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the GutenbergGutenbergThe 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/ repository on GitHubGitHubGitHub 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/. There are currently a handful of tickets planned for 6.8.2.
Specific times for RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). and General release will be announced in the 6.8 Release Leads room and will be based on availability of individuals helping with the release.
Targeted Fixes
One ticketticketCreated for both bug reports and feature development on the bug tracker. has high priority:
WordPress 6.8.2 is intended to be mainly focused on bugfixes introduced in 6.8, but some other bugs may be fixed in this release, depending on how self contained and straightforward the related changes are, and how confident are committers to ship these changes within a minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..
Get Involved with 6.8.2
Bug Scrubs will happen in the #core Slack channel during the times posted above. Everyone is welcome to attend these sessions to help moving milestoned tickets towards a resolution. Each of the open tickets is going to require development work along with testing and review.
You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. If you plan to run a 6.8.2 focused scrub, please get in touch with @audrasjb, @zunaid321 or @estelaris so it can be added to the release schedule.
General coordination for the release will happen in the #6-8-release-leads channel and decisions around code for the release will be made in the #core room.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2025 Recap
GutenbergGutenbergThe 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/ Release posts are online
The first AI Team chat takes place tomorrow at 16:00 UTC in #core-ai. Open to all – a great opportunity to learn more about ongoing projects, ask questions, and connect with the team.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 should be announced soon. Follow #6-8-release-leads for updates.
Discussion 💬
Discussion on TicketticketCreated for both bug reports and feature development on the bug tracker.#49442 (parse_blocks() Filter)
Ticket #49442, which proposes adding a filter to the result of parse_blocks(), is currently assigned to the 6.9 milestone. During the discussion, it was noted that the ticket still lacks test coverage (needs-test-info).
Creating a minimal test case was suggested to help move the ticket forward. It was also recommended to raise the topic in the Gutenberg repository for broader feedback and discussion.
Open Floor 🎙️
Improvements to the Docker Environment
@westonruter is working on several enhancements to the built-in Docker environment for wordpress-develop. The goal is to address various minor issues and “paper cuts” encountered during development. The first pull request with initial changes is ready for review, with more substantial improvements to follow in separate PRs. Feedback and reviews are welcomed to help improve the development environment for everyone involved.
PHPStan Code Quality
@justlevine has submitted several small pull requests aimed at improving code quality using PHPStan for version 6.9. The PRs are intentionally kept small to minimize conflicts and speed up integration. Support from reviewers and committers is appreciated to help keep the codebase cleaner and more maintainable. See #63268
“What’s new in GutenbergGutenbergThe 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).
This release continues the ongoing effort to refine the editing experience, improve accessibilityAccessibilityAccessibility (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 blockBlockBlock 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 HTMLHTMLHyperText 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 bugbugA 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.
Changelog
Enhancements
Block Library
Button Block: Add HTML Element selection in Advanced settings. (70139)
Comment Date: Convert Comment Date block settings to ToolsPanel. (70248)
Comment Author Name Block: Refactor setting panel to use ToolsPanel. (69407)
Comment Edit Link: Refactor settings panel to use ToolsPanel. (70247)
Comment Title: Refactor settings panel to use ToolsPanel. (70246)
Comments Pagination Block: Refactor settings panel to use ToolsPanel. (70245)
Embed Block: Refactor setting panel to use ToolsPanel. (69636)
File Block: Refactor setting panel to use ToolsPanel. (70189)
Form Input: Convert Form Input block settings to ToolsPanel. (70249)
Form: Convert Form block settings to ToolsPanel. (70253)
Latest posts: Change panel body to tools panel. (70200)
List Block: Refactor setting panel to use ToolsPanel. (69387)
Navigation Link, Navigation Submenu: Hide title UIUIUser interface controls while keeping attribute support. (70234)
Navigation: Refactor display panel to use ToolsPanel. (68011)
Post Title: Refactor settings panel to use ToolsPanel. (70229)
RSS: Refactor setting panel to use ToolsPanel. (70213)
Separator: Change html element option visibility. (70185)
ShortcodeShortcodeA shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site.: Add role attribute to content in block.jsonJSONJSON, 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.. (70164)
Video: Add option to set a track as default. (70227)
Components
ComboboxControl: Handle Unicode characters when matching values. (70180)
DropZone: Allow overriding the default icon. (70236)
Block Transforms
Adds transforms functionality to Post comments link and post comments number. (70287)
Fix: Click-through blur effect when gallery images have a caption. (69067)
Pullquote block: Cannot override cite element style via theme.json. (70260)
Social Link: Localize social service names for translations. (70199)
Social: Moves size settings to inspector controls. (70186)
Components
Ensure SVG Images Without a Width Attribute Are Displayed Correctly in FocalPointPicker. (70061)
FormTokenField: Fix filtering with full-width string. (70232)
Interactivity APIAPIAn 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.
iAPI: Make storePart argument optional in overloads. (70296)
Post Editor
Editor: Better normalize strings for hierarchical term filtering. (70178)
Block Editor
Flex Layout: Fix incorrect default alignment values for Vertical Alignment Control component. (68866)
Accessibility
Block Library
Button: Avoid focus loss when unlinking using keyboard. (70192)
Columns block: Don’t use ToolsPanelItem for Columns setting. (70210)
Details Block: Fix keyboard accessibility issues and allow list view selection to show up inner blocks. (70056)
Components
Toolbar: Adjust colors for dark mode support. (69278)
Experiments
Interactivity API
iAPI: Remove the full-page client-side navigation experiment. (70228)
Documentation
Docs: Added the missing ALT attribute to all images. (70225)
Docs: Remove misleading section from curating the editor experience. (70262)
Removed Empty line and corrected typo in inline document. (70203)
Replace “sidebarSidebarA 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.” with “panel” in tutorial.md. (70257)
The wp_admin_notice() function should be called instead of custom HTML for adminadmin(and super admin) notice in docs/how-to-guides/notices/README.md. (70231)
Updated small typo in inline documentation. (70187)
useDropZone: Refactor documentation to use the correct function syntax. (70286)
Video: Use a unique ‘key’ in the ‘TrackList’ component. (70263)
Tools
Testing
Cover Block: Add E2E Test for FocalPointPicker. (69077)
E2E: Add general end-to-end tests for templateLock functionality. (70160)
Fix end-to-end test for block API / filtered blocks. (51882)
Format .githubGitHubGitHub 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/ workflows .yml file. (70219)
Account for tests env port being overridden from 8889 in PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher unit tests. (70267)
First-time contributors
The following PRs were merged by first-time contributors:
We’re catching up with these posts now, as they have not been posted in a while. Since the recent releases have been smaller in scope, this post combines updates from both the 20.8 (May 14) and 20.9 (May 28) releases.
Both versions introduce a collection of enhancements, bugbugA 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, and improvements. These updates concentrate on refining the editor experience, improving accessibilityAccessibilityAccessibility (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 ensuring consistent design. Additionally, the releases incorporate under-the-hood updates focused on code quality and performance.
Prevent duplicate HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. main elements for improved accessibility.
Search BlockBlockBlock 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.: Move search setting to inspector.
Move Styles to top of sidebarSidebarA 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. navigation.
Changelog
20.8 (14 May) – Highlights
Prevent duplicate HTML main elements for improved accessibility.
The HTML Element option now includes validation to prevent duplicate <main> tags, enhancing accessibility and HTML compliance. (70002)
Search functionality in template swapping modal.
The template swapping modal now includes a search feature for smoother navigation. (69667)
Changelog
Enhancements
Create Block: Add --textdomain flag to create block tool. (69802)
Components
Guide: Make next and previous button text customizable. (69907)
Popover: Add virtual padding to prevent it from hitting the viewport edge. (69555)
Document Settings
Editor: Add search functionality to template swapping modal. (69667)
Block Editor
WidgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor: Don’t close the inserter when focusing outside it. (67838)
Editor
Use split view for metaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes only when canvas is iframed and “Desktop” view. (69958)
New APIs
Widgets Editor
Edit Widgets: Save lock control via actions. (69984)
Bug Fixes
GitHubGitHubGitHub 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/ Actions: Fix components changelog CI check. (70034)
Persist git credentials when publishing via lerna. (70007)
PluginPluginA 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 deprecation for ‘apply_block_hooks_to_content_from_post_object’. (69909)
ServerSideRender: Don’t render the previous error response in loading state. (69988)
ServerSideRender: Refactor fetchData to use useCallback and refs. (69237)
Block Library
Author, Author Name block: Fix PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher warning error when there is no context. (69949)
Block Editor: Allow editing invalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. blocks as HTML. (69902)
Block Editor: Prevent negative width values in Spacer block when used inside a row block. (68845)
Calendar block: Disable edit as HTML support. (69961)
Image: Avoid stale URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org when reselecting the same image from the library. (69985)
Latest Posts: Update content display labels to Display post content and Content length. (69839)
fix: Update the logic of fetching current URL in loginout block. (70031)
Block Editor
Block HTML: Add box-sizing property to prevent overflow. (70014)
Fix: Improve warning message and add spacing in HTMLElementControl. (70002)
MediaPlaceholder: Fix RegressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. with media URL input type to allow a local URL path. (70043)
Prevent block merging on blocks with the ‘disabled’ editing mode. (69918)
Components
Don’t mutate ‘ALL_CSS_UNITS’ default value in ‘useCustomUnits’. (70037)
Fix double border in ItemGroup when last item is focused. (70021)
ToggleGroupControl: Fix active background for empty string value. (69969)
Site Editor
Check user permissions before rendering export menu item. (69971)
Widgets Editor
Fix: Browser Warnings when closing keyboard shortcut modal. (69929)
Block APIAPIAn 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.
Fix: Missing conversion from jsonJSONJSON, 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. styled variable to CSSCSSCascading Style Sheets. variable. (69551)
Typography
Fix: Prevent FontSizePicker crash when no font size exists. (68733)
Icons
Remove width / height attributes from svg element. (43747)
Accessibility
Keyboard Shortcuts: Revert delete shortcut to access + z. (69931)
Fix: Remove an unnecessary @returntagtagA 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.) from this filterFilterFilters 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.docblockdocblock(phpdoc, xref, inline docs). (69960)
Code Quality
ServerSideRender: Use useLayoutEffect to update latestPropsRef. (69999)
Stylelint: Migrate configuration from JSON to JavaScript format. (69590)
List View: Add end-to-end test to verify pasting block styles via keyboard. (69979)
Try: Fix ‘wp-polyfill’ script dependents unit testunit testCode written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression.. (69912)
The settings of the search block have been moved from the block toolbar to the inspector panel for better consistency with other coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks. (70144)
Move Styles to top of sidebar navigation.
Move the Styles navigation item to the top position in the Site Editor’s main sidebar navigation, before Navigation, Pages, Templates, and Patterns. (68582)
Changelog
Enhancements
Base Styles: Update to modern Sass module system. (70135)
Post Publish Panel: Open view post links in a new tab. (70127)
Revert Adminadmin(and super admin) bar: Update the Edit Site link. (69974)
Block Library
Custom HTML: Add role attribute to content in block.json. (70154)
DOM: Add summary element to focusable elements. (70051)
Site Editor: Fix PHP warnings in gutenberg_get_site_editor_redirection. (70062)
URL: Handle HTML entities and ampersand in ‘cleanForSlug’. (70078)
Workflows: Persist git credentials when publishing packages via Lerna. (70058)
Block Library
Button: Limit scope of width style for link. (70054)
Image: Provide ‘defaultValue’ for ‘ResolutionTool’ component. (70122)
Post Template: Don’t rely on the default ‘ignore_sticky’ REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. value. (70020)
Components
Fix Styling for TextControland TextAreaControl in dark themes. (69640)
Fix URLPopover input handling to properly update value. (70156)
Post Editor
Editor: Honor rich/code editor settings when deriving the editor mode. (70080)
Hide “Create template part” menu from block settings dropdown for classic themes. (65568)
Block Editor
MediaPlaceholder: Fix potential error in ‘handleBlocksDrop’. (70090)
Accessibility
Editor: Add label inTextareaControl in CollabSidebar. (70133)
We’re catching up with these posts now, as they have not been posted in a while. Since the recent releases have been smaller in scope, this post combines updates from both the 20.6 (April 3) and 20.7 (April 22) releases.
Both versions introduce a collection of enhancements, bugbugA 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, and improvements. These updates concentrate on refining the editor experience, improving accessibilityAccessibilityAccessibility (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 ensuring consistent design. Additionally, the releases incorporate under-the-hood updates focused on code quality and performance.
Navigation BlockBlockBlock 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.: Add transparency slider for submenu background.
Navigation in Site View: Automatically expand all options.
Editor: Enable starter pattern modal for all post types.
Changelog
20.6 (3 April) – Highlights
Navigation Block: Add transparency slider for submenu background
This PR adds the ability to set a transparent background for Navigation Block submenus by enabling the alpha (transparency) channel in the color picker for the submenu background setting. (69379)
Changelog
Enhancements
Block Library
Feature: Adding support for more granular controls over the ToC block. (69063)
Navigation Block: Add transparency slider for submenu background. (69379)
RSS Block: Add option to open links in new tab/window and control rel attributes. (69641)
Block Editor
Add keyboard shortcut (cmd(ctrl)+option(alt)+v) to paste styles. (69196)
BlockPatternsExplorer: Hide scrollbar from sidebarSidebarA 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. if not scrollable. (69706)
Post Editor
Editor: Revert new default rendering mode for Pages. (69680)
Bug Fixes
BlockBreadcrumb: Wrap text node in span tagtagA 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.). (69605)
Fix Media & Text block preview alignment on larger devices. (67097)
Format Library: Ensure inline image with updates persist after removing the ‘width’. (69683)
Include blocks manifest build process in Webpack configuration to fix create-block bug with missing blocks manifest file. (69578)
Block Library
Featured ImageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. Block: Prevent default action on image click to fix linking to post. (69716)
Fix CategoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. List Block: Add optional chaining to taxonomyTaxonomyA 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. name. (69703)
Fix(embed-block): Only call setAttributes() when attrs change. (68141)
Fix: Correct ‘Displaying 1 – 0 of 0’ issue when no results are found. (69666)
Image block: Omit max width observer element in galleries. (69601)
PostCommentsForm: Fix submit button width regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. (69651)
Components
ComboboxControl: Replace undefined variable usage with color-mix for disabled selection. (69621)
CustomSelectControl: Use dynamic fill color for check icon. (69626)
Fix autocomple UIUIUser interface flicker when deleting trigger prefix. (69562)
Update NumberControl stepping to match HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. number input stepping. (34566)
Block Editor
LinkControl: Fix visually Duplicative label and placeholder. (69620)
PatternsExplorerModal: Fix empty patterns in starter content category. (69629)
Post Editor
Post Template Panel: Render create-new-template-modal over post-template-panel. (69713)
Global Styles
Site Editor: Make the text “Custom Styles” translatable. (69677)
Site Editor
Set IFRAME_REQUEST constant for classic theme site preview. (69535)
Document Settings
PostStatus: Prevent form submission from refreshing the page. (69526)
Accessibility
Document Settings
Post Template Panel: Preserve parent modal when closing template creation dialog. (69724)
Block Library
Site Title: Prevent saving and rendering a value made of only spaces. (69628)
Reference splitTask from interactivity package in documentation. (69602)
Storybook: Update ToolbarItem and ToolbarDropdownMenu exports. (69618)
Update the list of GutenbergGutenbergThe 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/ versions in WordPress versions. (69700)
Navigation in Site View: Automatically expand all options.
This PR changes the default state of navigation submenus in Site View from collapsed to expanded, making all navigation options immediately visible to users without requiring manual expansion. (69343)
Editor: Enable starter pattern modal for all post types.
This PR fixes the starter pattern modal so it works for all post types, not just pages. It removes the restriction that was limiting the modal to only appear when creating new pages. (69753)
Changelog
Enhancements
Format Library: Add a feature to set the alpha value to Highlight. (67525)
Playwright end-to-end utils: Add new emulateNetworkConditions helper. (69865)
Block Library
Details: Enable all non-interactive formats. (68741)
Navigation in Site View: Automatically expand all options. (69343)
Remove experimental status from comments count and comment link blocks. (69832)
Table Block: Preserve Column Alignment when Pasting Markdown Tables. (69322)
Tag Cloud: Remove unnecessary full-width padding. (69725)
Block Editor
Remove truncation from media tab preview tooltips. (69741)
Support passing updater function to ‘setAttributes’. (69709)
Media
Remove @shopify/web-worker Dependency from packages/upload-media. (69816)
Bug Fixes
DataViews: Ensure consistent display of primary ellipsis in list layout. (69846)
Scripts: Fix blocks manifest generation when directory name has space. (69766)
Block Library
Enhance Featured Image Block: Don’t include interactive elements within an element. (69730)
Featured Image: Don’t render empty Resolution tools panel if media is not set. (69805)
Fix: Background wrapper for ‘Button Inside’ option. (69624)
Fix: Update the static text and make them translatable in the Blocks example. (69859)
Fixed Media & Text Block – Image not rendered properly on frontend when inside stack. (68610)
Query LoopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.: Don’t overwrite the ‘query.inherit’ attribute value. (69698)
Query Loop: Fix ‘undo trap’ and improve debouncing for ‘Keyword’ control. (69845)
ToC: Fix condition for ‘Limit heading levels’. (69811)
ToC: Fix related block attribute persistence. (69734)
Block Editor
Block Tools: Prevent showing block toolbar when block interface is hidden. (69795)
Block drag & drop: Enable mouse click on input/textarea elements in Firefox. (69781)
Fix: Restore static properties on deprecated __experimentalLinkControl. (69860)
Fix: Space visualizer showing previous value. (69747)
Post Editor
Fix: Save custom template with non-latin slug. (69732)
IframeiframeiFrame 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.: Don’t enable for block themes in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. if v2 blocks exist. (69778)
Document Settings
PostPublishPanel: Fix post title overflow. (69804)
Patterns
Editor: Enable starter pattern modal for all post types. (69753)
Components
UI Components: Add theme support for FormTokenField and ComboboxControl. (69638)
Accessibility
DataViews: Always show primary action for list layout if hover isn’t supported. (69876)
Block Library
Navigation Link, Navigation Submenu: Remove the title attribute controls. (69689)
Create Block: Improve support for blocks manifest and relevant Core APIs. (69767)
Docs: Improve document and parameters in render_block_core_* function. (69856)
Fix: Incorrect Type of wp_widget_factory in render_block_core_legacy_widget Doc Block. (69775)
Fix: Expose TypeScript types for subcomponents. (69619)
Latest Posts block: Add missing @globalPHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher documentation. (69763)
Code Quality
Block Parser: Remove description for singular since tag. (69799)
Fix Documentation inconsistencies in Block Parser classes. (69785)
Stylelint-config: Add stylelint-scss as a peer dependency. (69685)
Update metadata fields requested from server. (69801)
Components
Update gradient-parser dependency from 0.1.5 to 1.0.2. (69783)
Tools
Testing
Automated Testing: Add GitHubGitHubGitHub 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/ Actions workflow for Storybook smoke testing. (69679)
E2E: Split list view keyboard shortcuts into multiple tests. (69231)
Workflows: Ignore ‘widgets’ for manual backports. (69792)
Build Tooling
Workflows: Ignore ‘block-serialization-default-parser’ for manual backports. (69791)
First-time contributors
The following PRs were merged by first-time contributors:
@Debarghya-Banerjee: Fix: Incorrect Type of wp_widget_factory in render_block_core_legacy_widget Doc Block. (69775)
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Tickets
Create a list of reviewers with publishing privileges so an author knows who to contact to move things forward once the post has been peer-reviewed.
Create a list of volunteer authors who can help with drafts. For example: GutenbergGutenbergThe 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/ Release Manager could fulfil their responsibility by tagging those volunteers.
Create a GitHubGitHubGitHub 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/ action from wordpress/gutenberg that triggers a Slack message to Core on Gutenberg release.
This solution can also automate a message about rc1 in Slack tagtagA 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.) volunteers in #core-editor
@jorbin replied that there might be consent issues and it’s also hard to predict who is active on a day in/day out basis. Starting from a message in #core or #core-editor for someone with publish permissions to review and publish could be enough.
To be discussed 🙂
Open floor 🎙️
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe is today!
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 should be announced soon. Follow #6-8-release-leads for updates.
As a follow-up to this post, he asked the following to be discussed:
After a couple of weeks, I’m almost done on reviewing the Workflow Keywords sequence. I only need some extra info in the committing part as is the part I’m less knowledgeable, so I would need some committers to help me out on the review
[I] need committers to help with the revision of the Workflow Keywords (specially the committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and backportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.
Some discussion happened in the Core Slack channel about this post/proposal.
To sum-up, some committers pointed out that:
@jorbin: This post seems to make the assumption that just because there is a patchpatchA 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. and the patch has no flaws, that it should be committed, but if something should be committed isn’t just a question of if there is a patch ready, it’s also things such as: Does this fit within the current priorities? Is this going to cause issues with future backwards compatibility? Are there alternative solutions that haven’t been considered that should be? How risky is this to commit? What other teams would be affected by this change? Have they been given a chance to chime in?
@desrosj: The crux of the post seems to suggest we can’t create a report for tickets that need a code review with the current keywords. Wouldn’t a report that shows tickets with has-testing and has-patch but does not have commit accomplish the same thing?
@sirlouen pointed out that the post is not completely assuming that every patch perfectly reviewed must be committed, but every patch perfectly reviewed should be considered by committers with more priority than patches from scratch.
The discussion then switched to patches that are reviewed and tested, and waiting for a committer review and commit:
@jorbin: Bringing those tickets up during bugbugA 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. scrubs can be a great way to get attention on them, [but] just because it fits [someone’s] definition of 100% baked doesn’t mean that a committer is going to agree.
@audrasjb: The best way to help these tickets is to ask to move them into the current milestone.
@jorbin: There are about 75 bug gardeners who can modify milestones in addition to all of the committers. In addition, there is nothing that would prevent at the end of the bug scrub a post along the lines of: “After this scrub, we think that the following tickets should be included in 6.8.2 and the following ones in 6.9”. Once someone has demonstrated enough good judgement, they will likely be given bug gardener status so that they can do it themselves.
@justlevine wanted to bring attention to ticketticketCreated for both bug reports and feature development on the bug tracker.#61175: “Beyond the usual i could use a bit of help from people better skilled at WP CI/CD (PHPStan passes locally, but isn’t discovering certain symbols when run on CI)”. See the related GitHub PR.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
Proposal concerning Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords
He asked the following: “Need committers to help with the revision of the Workflow Keywords (specially the committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and backportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.”
Open floor 🎙️
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.
You must be logged in to post a comment.