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.
Thank you to all who volunteered as interested in serving on the WordPress 6.8 release squad! After collecting all of the volunteers, reviewing active initiatives and tickets currently in the milestone, contributor availability in various areas, and planned events or holidays the following squad, timeline, and focus has been assembled.
Release Squad
Release LeadRelease LeadThe community member ultimately responsible for the Release. – Matt Mullenweg
This squad continues the experiment that started in 6.7 of merging the MarComms (Marketing and Communications) Lead with Release Coordination in order to gather more feedback on that experiment. This can change during the process for future releases if needed. The squad is also a bit smaller than usual because of this release being a polish and 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. fix release. Also of note, the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead and Editor Tech Lead roles have been combined into a single “Tech Leads” role as part of the continued initiative to support a more closely coordinated effort across 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/ and Core.
Aaron Jorbin has volunteered to continue managing tickets and will organize minor releases as necessary for the remainder of the 6.8 release cycle.
Release Timeline
As a reminder, here are a few of the key milestones for the release:
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. 1: March 4, 2025
Release Candidaterelease 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). 1: March 25, 2025
After evaluating the current active initiatives, there will likely be fewer features ready to ship when compared to other recent major releases. As a result, 6.8 will focus primarily on being a polish and bug fix release. New features will be considered if deemed reasonably ready.
A WordPress release is put together by the entire community and the release squad only represents a fraction of the contributors to a release. If you are looking to get involved, please join the #core channel in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. where there are weekly chats on Wednesday at 20:00 UTC and bi-weekly new contributor onboarding meetings on the 2nd and 4th Wednesday of each month at 19:00 UTC.
Benjamin Zekavica is joining as a Core Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for the first time, and along with Francesca Marano and Jean-Baptiste Audras. He aims to get up to speed, gain new experiences, and strengthen the Core Team together.
Forthcoming releases 🚀
New maintenance release: 6.7.2
The maintenance release WordPress 6.7.2 was officially released on February 11 and is now available for download. Thanks to everyone who contributed to this release and helped with testing at the release party!
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8
Next 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: 20.2
Gutenberg 20.3 is due for release on February 19, 2025. For more insights into the new version, here is a detailed overview of all the changes and new features in the Gutenberg release.
Discussion 🤔
Improving 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.TicketticketCreated for both bug reports and feature development on the bug tracker. visibility
@desrosj shared a proposal to improve the visibility of unit test-related tickets. See more here: #7907. A new “tests” focus has been added in 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.TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to highlight tickets where tests need to be added or improved. @joemcgill clarified that this focus is specifically for tickets where new tests are being added or enhanced, not for tickets that already include tests as part of feature work.
@jorbin discussed that “Task (blessed)” tickets should only be handled by the release squad. If this is not the case, the categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. should likely be re-evaluated.
Open Floor 💬
WordPress 6.8 | TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. update
@audrasjb shared updated stats for the upcoming WordPress Release 6.8 release with detailed information.
Ticket Status
On the 361 tickets in the milestone:
160 tickets are closed as fixed
201 tickets are still open (14 of them were reopened for further fixes)
@audrasjb encourages committers involved in version 6.8 to commit tickets that are ready. A Trac report for commit-ready tickets has been shared. Starting tomorrow, tickets with the early keyword will be moved to milestone 6.9, and a Trac report for those tickets is also available. A milestone for WordPress 6.9 was created on February 11, during the latest 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) scrub.
Gutenberg Packages update status
@joemcgill mentioned that the initial sync of Gutenberg (GB) packages was completed last week, allowing features to be tested directly in trunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. Ongoing syncs will continue after upcoming Gutenberg releases and as needed for 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. There are several pending pull requests (PRs) to port PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher functionality to trunk, which still require review and merging. These PRs are tagged with the gutenberg-merge keyword in Trac. See #62887
Recommended PHP version information
@Mdxfr raised a question about the recommended PHP version for WordPress 6.8, particularly for performance and 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 compatibility. While WordPress is compatible with PHP 8.3, full compatibility is still being assessed. This will be discussed further in the next Dev Chat, where a Core Team representative will gather additional information from the Hosting Team.
Thanks to @francinafor helping review this summary.
The full chat log is available beginning here on Slack.
WordPress Performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Discussion of performance tickets for the upcoming 6.8 release:
#39242 (Add caching to count_user_posts()) – Jonny Harris plans to commit
#62503 (Add speculative loading support) is now waiting for follow up reviews
Performance Lab 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 (and other performance plugins)
A reminder that the next version of the Performance Lab plugin will be this Thursday.
The release branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". has been cut and the PR to prep the release has been opened.
Needs testing and then we’re good to go for Thursday.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
Additional items will be referred to in the various curated agenda sections below. 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.
Announcements
Introducing Core Team Reps for 2025. Thanks to @francina, @audrasjb, and @benjamin_zekavica for taking over the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. role for 2025.
Forthcoming releases
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8
Next 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: 20.3
The next Gutenberg release will be 20.3. It is scheduled for February 19 and will include the following issues.
Discussions
The discussion section of the agenda is to provide a place to discuss 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.
Topics this week
Proposal: Make 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. tickets easier to distinguish – @desrosjfollowed up to this proposal by opening a Meta Trac ticket requesting the addition of a `tests` focus to give this a try.
You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.
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 if you intend to be available during the meeting for discussion or if you will be async.
Now that the nominations process for Core Team Reps has concluded, I’m pleased to announce that @francina and @audrasjb have agreed to serve as CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps for 2025 with @benjamin_zekavica joining them in a mentorship role to start the year. This team brings deep experience to the role, with both @francina and @audrasjb having served multiple times, going back to 2020. This structure ensures continuity while also allowing us to welcome new contributors to this role.
About our new Team Reps
Francesca Marano
Francesca Marano is the Head of Partnership at Patchstack, a cyber security company helping companies and software developers to identify & 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. vulnerabilities in open-source code. Francesca co-led the release of 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/ 5.3, 5.4, 6.2, and 6.3. She mentored multiple releases, including 5.6, the first-ever women and non-binary squad. She served as the Core Team global representative and previously as the Community Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.. One of the things she is most proud of is the blogblog(versus network, site) C+B, which she founded in 2013. It helped many creative female entrepreneurs find their path throughout the years. As an accomplished educator, community leader, and public speaker, you can find her around the world talking about WordPress, community, open-source, women in tech, leadership, and small businesses.
Jb Audras
Jb Audras hails from Ardèche (France), is currently the CTO of Whodunit, a well-known French WordPress agency, and is one of the WordPress Core Committers. He started using WordPress in 2007, has already served as the 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) Team Rep and Core Team Rep a few years ago. Jb led multiple maintenance and security releases and played a key role in a dozen major releases, most recently as the Core Tech Lead of WP 6.6 or TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead for WordPress 6.8. When not contributing to WordPress, Jb can be found in various cliffs, seeking new climbing challenges.
Benjamin Zekavica
Benjamin Zekavica is a web developer from Aachen, Germany, with 16 years of experience in the field. A dedicated WordPress user since 2013, he has been actively involved in the community since 2015. He contributed to WordPress 6.5 as the Design Lead and has been working on 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/ project since version 5.0. Beyond development, Benjamin is deeply engaged in the WordPress community, serving as a mentor for the Core Team and actively participating in WordCamps as an attendee, volunteer, organizer, and speaker. His passion for open-source collaboration and community building makes him a valued contributor to the WordPress ecosystem.
About the Team Rep role
The role of Team Rep in the WordPress project dates back to 2012. Anyone who serves as a “Team Rep” is responsible for communicating on behalf of the Core team to the other contributor groups via team updates, as well as occasional cross-team chats. While not formally part of the role description, folks serving in this role have also facilitated the Core team’s weekly Dev Chat meetings for the past several years. Full details on the Team Rep role is on the Team Update site.
The role is intentionally called “Team Rep” rather than “Team Lead” because it is primarily an administrative position. While people elected as Team Reps will generally come from the pool of folks that people think of as experienced leaders, the Team Rep role is designed to change hands regularly.
On behalf of @mikachan and myself (@joemcgill), thank you for allowing us to serve in the role during the past year. It’s an absolute honor to be able to support this amazing community of individuals who share their time, energy, and talents with the WordPress software project. Congratulations to our new Team Reps! We are confident that the role is in very capable hands.
This time, due to the smaller sizes of the releases, this post contains information for both the 20.1 (22 January) and 20.2 (5 February) releases.
“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 Editor.
Although both releases were smaller in size, they contain many useful enhancements, bugfixes and more. Apart from the highlighted changes, work continued on updating the 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. settings to use the ToolsPanel. Both updates ship with 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) updates as well.
20.1 (22 January)
Content preview for pages in DataViews
Menu name shown in list view
Color pickers in Navigation, Social Icons and Post 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. get Clear control
Changelog
20.2 (5 February)
Content block: color options for headings added
Changelog
20.1 (22 January)
Content preview for pages in DataViews
The DataViews got enhanced by a new preview functionality to show the page’s content instead of the featured image, similar to patterns and templates. You can activate this feature in the settings and switch between featured image and content preview. This setting persists across all three views, table, grid and list. (67278)
Menu name shown in list view
In the list view, the name of a menu is now shown instead of the block name “Navigation”. If the menu is changed, the name is updated as well. (68446)
Color pickers in Navigation, Social Icons and Post Featured Image get Clear control
Previously, color options at the Navigation, Social Icons and Post Featured Image blocks did not have a Clear control to easily remove the color. This applies to every color option on these blocks. (68454, 68564, 68525)
Other Notable Highlights
Enhancements
ESLint: Improve regex for valid-sprintf rule to handle ‘%%’. (68270)
Simplify sprintftranslationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. for percentage widths. (68587)
Block Library
Archive Title Block: Refactor settings panel to use ToolsPanel. (67915)
Author Name: Refactor settings panel to use ToolsPanel. (67953)
Block Editor: Move state logic inside ‘BlockRenameModal’. (68560)
Editor: New default rendering mode for editor via post type supports. (68549)
Document Settings
Change “Swap” to “Replace” for Template Action. (68234)
DataViews
Add: Media field changing ui to Dataviews and content preview field to posts and pages. (67278)
Bug Fixes
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Check post-type support before requesting autosaves. (68680)
Fix text direction for URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org and email fields in block editor for RTL languages. (68188)
Navigation Link UIUIUser interface: Remove onClose from onSelectBlock. (67760)
Post Featured Image: Adds control to clear the the overlay color. (68525)
Site Logo: Prevent uploading multiple images via drag and drop. (68618)
Social Links: Don’t prepend URL fragments. (68655)
i18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Make example label for Comments Pagination Next block translatable. (68373)
i18n: Make example translatable in comments-pagination-previous. (68374)
Components
Duotone: Fix scrollbars displayed on Duotone Control. (67187)
Fix SCSS Media Query Compilation Issue in Storybook. (68464)
Restore Non-Themed Text Colors for optimizeReadabilityFor. (68472)
StoryBook: Fix error that could occur when loading compiled CSSCSSCascading Style Sheets.. (68526)
Site Editor
Classic theme preview: Remove adminadmin(and super admin)-bar class name. (68519)
Fix: Site Editor Template part is missing an icon in the 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.. (68653)
Navigation: Fix typo in history.navigation's function call. (68623)
Block Editor
Differentiate ‘Copy’ and ‘Copy styles’ snackbar confirmation messages. (68167)
Refactor: Separate input form styles to a dedicated stylesheet. (68501)
Update percentage strings to be translatable. (66323)
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: Fix the logic path that merges plain objects. (68579)
Accessibility
Nux: Standardize reduced motion handling using media queries. (68423)
Block Library
Fix Inconsistent Labels for Lightbox Feature. (68261)
Site Logo: Prevent focus loss when updating media from the sidebar. (68621)
Standardize reduced motion handling with media queries. (68315)
Components
Fix usage of tooltip in the Circular option picker. (68602)
Post Editor
Edit Post: Standardize reduced motion handling using media queries. (68426)
Widgets Editor
Customize Widgets: Standardize reduced motion handling using media queries. (68425)
Block Editor
Remove unnecessary CSS order property for the contrast checker in the Color hook. (68055)
[core-data] Document and add types for dynamic actions and selectors. (67668)
docs: Fix param name in gutenberg_add_can_update_block_bindings_editor_setting(). (68390)
docs: Fix return type on gutenberg_register_block_module_id(). (68393)
Block Library
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.: Remove unused styles. (68615)
Site Logo: Remove unused argument for ‘mediaUpload’ function. (68617)
Global Styles
Remove unused prop for ‘BackgroundImageControls’. (68616)
Post Editor
Document Outline: Use block client ID as unique ‘key’. (68502)
Edit Widgets and Base Styles: Standardize reduced motion handling using media queries. (68427)
Components
Standardize reduced motion handling using media queries. (68421)
Block Directory
Standardize reduced motion handling using media queries #68419. (68420)
Site Editor
Edit Site: Add tsconfig.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. validation for package. (67406)
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: Remove ESLint rule for deprecated functions. (68590)
First-time contributors
The following PRs were merged by first-time contributors:
@AhmarZaidi: Update percentage strings to be translatable. (66323)
Previously, it was only possible to change colors for text, background and link on the content block. With this update, the color of all headings and each individual heading level can be changed. (67783)
Other Notable Highlights
Enhancements
Block Library
Details block: Add name attribute for exclusive accordion. (56971)
Search Results Title Block: Add dropdown menu props to Tools Panel component. (68763)
Spacer: Add dropdown menu props to Tools Panel component. (68761)
Term List Block: Refactor settings panel to use ToolsPanel. (67955)
Design Tools
Position: Refactor “Position” controls panel to use ToolsPanel instead of PanelBody. (67967)
Post-content block headerHeaderThe 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. color support. (67783)
Navigation Submenu Block: Add example preview. (68378)
Bug Fixes
Fix: 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._doing_it_wrong() for experimental-link-color. (68408)
Docs: Update links to HTTPSHTTPSHTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information.. (68888)
Lint: Fix broken URL reference for stylelint user guide configuration. (68706)
Used https in main-dashboard-button.md file. (68883)
wp-env: Add phpMyAdmin and multisitemultisiteUsed to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site support to the documentation. (68125)
Code Quality
Inline Commenting: Change the PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher compat directory. (68846)
Fix: Remove invalid param from wp_register_style() in gutenberg_enqueue_stored_styles(). (68409)
Fix: setcookie() $value must be string in Gutenberg_HTTP_Signaling_Server::Handle_read_pending_messages(). (68411)
Block Library
Gallery: Remove unused inline menu styles. (68776)
Move HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. element help messages to the block library utils. (68708)
Unify block title with a strict title case. (51912)
Video: Fix reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. component warning error. (68762)
Post Editor
Editor: Children prop to accept ReactNode. (68839)
Editor: Combine selectors in the ‘Header’ component. (68697)
Editor: Standardize reduced motion handling using media queries. (68424)
Components
Box Control: Add Runtime Check & Conditional Types for presets and presetKey Props. (68385)
Remove unnecessary Tooltip component from linked button. (68498)
Block Editor
Clean up unused utils of spacing size control. (68794)
Template Editor
Editor: Update post-type support key for new default rendering mode. (68745)
Tools
Build Tooling
Fix Duplicate Entries for 19.7.0 in changelog.txt. (68836)
E2E: Fix WP Editor 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 test. (68872)
WordPress 6.7.2 Release Candidate 2 (RC2) is available for testing! Some ways you can help test this minor release:
Use the WordPress Beta TesterpluginPluginA 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
As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
6.7.2 RC2 is a release candidaterelease 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). for a maintenance release with a focus on bugs introduced in WordPress 6.7. In total, this RC features fixes for 35 bugs throughout Core and the Block Editor. This also includes one fix for Twenty Twenty-Five which means a new version of that default theme will be released. Please see the RC1 announcement for a list of fixes. New fixes in RC2 are:
#62907 – 6.7 broke accordion styles for themes/plugins using `do_accordion_sections()`
#62597 – WordPress 6.7 sizes=”auto” is messing 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. on chrome mobile.
Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.7 branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
The final release is expected on Tuesday, February 11th, 2025. This date is subject to change if any issues with RC2 are discovered. Coordination will happen in 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/SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.#6-7-release-leads channel, and releases are always packaged and tested in #core.
A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.7.2 depends on proper testing, so please lend a helping hand.
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8
Next 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: 20.2
Gutenberg 20.2.0 was released on February 5. It included the following issues. For the last several releases, the “What’s new in Gutenberg” posts have been paused due to the team’s capacity. If anyone is interested in helping with these posts, please contact @mamaduka.
The PR is ready for another review. There is an issue causing the wp-polyfill script being bundled but is not a blockerblockerA bug which is so severe that it blocks a release. for the sync.
WordPress 6.8 Roadmap
@krupaly2k was still working on this with support from @jeffpaul and feedback from release squad members.
The Roadmap to 6.8 post was published following the meeting.
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/. feedback needed
There was discussion about whether this should be fixed on the server side or in the client.
@jorbin suggested trying to get some tests written that show the 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. in the server in order to help drive a fix.
@joemcgill said that fixing server side is a good idea, but if a client side fix could resolve a user issue then we should pursue that as well.
WordPress 6.8 is set to be released on April 15th, 2025. This release continues refining foundational features introduced in previous versions, focusing on improving data views, query loops, and 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. interactions. It introduces a more streamlined design experience with a “Zoom Out” editing approach, expanded style controls, and enhanced typography options. Additionally, new “Write” and “Design” modes provide users with greater flexibility when editing content. 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. developments, including the Block HooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and Block Bindings APIs, aim to enhance extensibility, while speculative loading integration and performance optimizations seek to improve site speed. 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) improvements and ongoing support for PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.x ensure WordPress remains user-friendly and forward-compatible.
As always, what’s shared here is being actively pursued, but doesn’t necessarily mean each will make it into the final release of WordPress 6.8.
For a more detailed look at the work related to the block editor in WordPress 6.8, please refer to the 6.8 release cycle page and review the currently open Iteration issues. These Iteration issues reflect actively scoped work targeted for this release. Additionally, to gain insight into ongoing developments and future enhancements, you can explore the discussions and updates shared in the latest Gutenberg pull requests and tracking issues.
Design Improvements
The design focus will be on polish and fix, clearing ‘needs design feedback‘ issues.
The Style Book provides a comprehensive overview of your site’s colors, typography, and block styles in an organized layout. Each block example and style group is labeled, making it easy to preview and understand your theme’s current design settings. For classic themes that support the Style Book, site patterns have been relocated to Appearance > Design > Patterns, consolidating all design-related functionality from the Site Editor into one place. Previously, patterns were listed under Appearance > Patterns.
In zoom-out mode, users can now apply different section styles and designs directly from the toolbar, cycling through them and inspecting them in the context of the rest of the page. This enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. streamlines the decision-making and production process (#67140).
Another user experience improvement can be found in the list of fonts: Each font family is now previewed in the font picker dropdown and gives users a better indication as to what the font will look like (#67118).
The outcome of the Image manipulation methods are now better communicated in the block editor. The success notices are now displayed at the bottom of the editor. The notices also come with a handy Undo link to revert to the original if necessary (#67314, #67312).
Block supports: Show selected item in font family select control. (#68254)
Fix: Ensure consistency in editor tools for navigation buttons and delete options. (#67253)
Global Styles: Fix handling of booleans when stabilizing block supports. (#67552)
Support for Speculative Loading
Building upon the success of the Speculative Loading plugin, which has over 40,000 active installations, WordPress 6.8 plans to integrate speculative loading into coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. This feature utilizes the Speculation Rules API to prefetch URLs dynamically based on user interaction, aiming to improve performance metrics like Largest Contentful Paint (LCP). The current proposal has default configuration employing conservative prefetching to ensure safety and compatibility, but feedback is requested on this. Developers will have access to filters for customization, allowing adjustments to the speculative loading behavior as needed (#62503).
Polishing the 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.
By polishing the query loop we are focusing on enhancements like 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. by year, pagination, fetching results by adding offset, block spacing improvements, Sticky post not working when query type is default in editor, query loop depth set etc.
(This data comes from WordPress 6.8 Editorial Tasks and 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/ releases from 19.4 to 20.2.)
Working on fixing and enhancing List layouts, grid layouts, text truncation, padding and spacing in grid and list.
Zoom out to compose with patterns
With patterns getting more feature-rich and pervasive. This effort aims to provide a new, high-level approach to building and interacting with your site, with several key features in development:
Improvements to UXUXUser experience for dragging patterns (e.g. Hide Zoom Out Inserters when dragging into canvas).
UX improvement on Zoom Out (e.g. Rely on Zoom level instead of Zoom Out, Zoom Out shortcut on Windows, Add Keyboard shortcut in editor, Move default background to the 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. component, Zoom animation scrollbar fix)
Interactivity API (Not on track for WordPress 6.8)
In WordPress 6.7, work focused on important improvements to enhance the stability and simplicity of the Interactivity API internals, the introduction of new APIs like getServerState/getServerContext and wp_interactivity_get_element, improvements to the types, and progress on the Gallery block lightbox and Query block’s Instant Search.
In WordPress 6.8, the primary focus will be on:
Enhancing client-side navigation, advancing full page client-side navigation while addressing and improving the limitations of region-based client-side navigation.
Finishing the lightbox of the Gallery Block and the Instant Search functionality for the Query and Search Blocks.
Work is also continuing to improve the documentation. Follow this tracking issue for more information.
Support length property on strings and arrays on the server
Interactivity API directives support 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. data attribute characters on the server
Support for marking store actions that require synchronous event access (#68097)
The Block Hooks API is an extensibility mechanism that allows you to dynamically insert blocks into block themes. In WordPress 6.8, work will continue on improvements of Block Hooks.
HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API
HTML API enhancements will be focused on HTML process speed improvements and new features like introducing safe composable HTML templating, Inner and outer HTML support.
Various security-related enhancements are planned for WordPress 6.8, the most significant of which is the switch to using bcrypt for password hashing. This includes improvements to the algorithm that’s used for storing application passwords and security keys. A dedicated post will be published soon on make/core covering these changes in detail.
Additional performance improvements
A variety of initiatives are also focused on improved loading times like Lazy load post 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., Lazy load user capabilities in wp_user object, ORDER by RAND() speed improvements, cache the result of get_uploaded_header_images(), Improve cache generation in WP_Query class, and Cache duplicate calls to WP_Theme_JSON::sanitize. In preparation for the WordPress 6.8 release, several key performance improvements have been implemented in the block editor and collectively contribute to a more responsive and efficient editing experience.
Navigation Block Optimization: Addressed performance issues in the site editor when handling navigation blocks with multiple submenu items, enhancing responsiveness during template editing (#68875).
Selector Efficiency Enhancements: Improved the isBlockVisibleInTheInserter selector to prevent unnecessary computations, resulting in a more efficient block editor experience (#68898).
StyleBook Resizing Improvement: Resolved issues causing unsmooth resizing in the StyleBook for classic themes, leading to a more fluid user experience (#68978).
Event Handling Optimization: Introduced the withSyncEvent action wrapper utility to streamline event handling, reducing potential performance bottlenecks (#68097).
Inserter Selector Optimization: Implemented changes to avoid unbounded requests in inserter selectors, enhancing the efficiency of block retrieval processes (#66817).
Review usage of target=”_blank” in the adminadmin(and super admin)
Title attributes galore. They serve no useful purpose.
Submit buttons on form fields in the Add Media panel
Semantic elements for non-link links
Enhancement: Add a wrong password message on password protected posts
Code Editor: Linter (HTMLHint) should show error if checkbox doesn’t have associated <label>
Media uploader does not restrict file upload `accepts` parameters based on current context
Twenty Twenty: with horizontal menu, submenu should be dismissible
Add prefixes to all admin notices (Warning, Error, Success, Info)
Improve the admin notices accessibility
Fix and improve arranging metaboxes
Add a mechanism for accessible tooltips in core
Twenty Twenty: Menu + Search can cause a scroll jump on close
Excess text read with errors in Media Library
The WordPress core password reset needs to pre-populate the username to meet WCAGWCAGWCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.2
Validation of custom links in admin menu not accessible
Simplify add_new_item labels for core post types
Update the screen-reader-text CSSCSSCascading Style Sheets. class and its local implementations
Missing “submit” button – bad accessibility
Bring in lighter background for admin
Add padding and color changes to buttons and inputs
Change font weight of settings and other similar labels
Adjust background alternate row on post and page tables
core/site-title block adds aria-current to the blogblog(versus network, site) page when it is not the front page
get_custom_logo does not apply the aria-current attribute in all cases
Improve HTML semantics in Site Health Info tables
Consider removing title attributes from Classic Editor scripts
If you have something you’re working on that you don’t see reflected in this post, please share a comment below so we can all be aware! If you’re reading this and want to help, a great place to start is by looking through each issue associated with each area or by diving into the Polish board where a curated set of issues are in place that anyone can jump in on.
WordPress 6.7.2 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:
Use the WordPress Beta TesterpluginPluginA 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
As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
6.7.2 RC1 is a maintenance release with a focus on bugs introduced in WordPress 6.7. In total, this RC features fixes for 32 bugs throughout Core and the Block Editor. This also includes one fix for Twenty Twenty-Five which means a new version of that default theme will be released.
The following coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets and PRs are included:
#62534 Pagination broken in adminadmin(and super admin) for categories / tags / plugins
#62491CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. accordion height fills screen
#62494 Some links on the left controls of theme customise non responsive
#62140 Relax restrictions around registration of 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. metadata collections
#62422 Can’t edit pages after update to 6.7 and also later after downgrade
#62504 Checking “Uncategorized” categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. adds all categories with an ID starting with 1
#62523 Can’t register Block Templates for CPTs with an underscore “_” character in the key
#62639 Block HooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.: Wrongly typed context when updating wp_navigation post 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.
#62269 WP_HTML_Processor::next_token() cannot be extended in subclasses to keep track of state
#62290 Unable to seek to any bookmark in HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Processor
#62363 HTML 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.: Expects closer should report true on svg:input element
#62427 HTML API: Next 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.) tag name query is c
#62522 Whitespace can trip up WP_Interactivity_API::_process_directives() when there is a core/buttontext block binding
#62380 About page: ‘See everything new’ link can extend outside its container
#62646PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Warning in 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/. when post_type doesn’t support post-formats, but a post-format 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. is applied.
#62434 Missing Escaping functionality for async-upload.php Some Variable
Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.7 branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
The final release is expected on Tuesday, February 11th, 2025. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in 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/SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.#6-7-release-leads channel, and releases are always packaged and tested in #core.
A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.7.2 depends on proper testing, so please lend a helping hand.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
Additional items will be referred to in the various curated agenda sections below. 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.
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8
WordPress 6.7.2 is scheduled for February 11, with a 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). planned on February 4.
Next 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: 20.2
The next Gutenberg release will be 20.2, tentatively scheduled for February 5. It will include the following issues.
Discussions
The discussion section of the agenda is to provide a place to discuss 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.
Global Styles – Should custom CSS be moved out of global_styles and into it’s own dedicated function? – An issue occurs when a third party 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 enqueues a stylesheet via wp_enqueue_scripts without specifying a priority
Aiming to include in 6.8
Storybook – Classic theme preview: Potential issues with JavaScript loaded by themes – When a classic theme adds the theme support for editor-styles, a menu item called “Design” replaces the Pattern menu, and following this link shows the dark 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. and an 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. with the site embedded.
Gutenberg High priority 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. – Users of classic themes can access and use parts of the Site Editor but its a broken experience
Moving the autosave notification outside the block editor canvas – Autosave notification inside 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. editor
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): Inconsistent Copy/Cut Behavior Between Keyboard Shortcuts and Block Menu Actions – Bug
Additional CSS field is no longer full-height in Site Editor – 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. issue of full height is not showing in Additional CSSCSSCascading Style Sheets.. With GB 20.0 and WordPress 6.7 it smaller height of additional css box instead full height box
Props to @krupaly2k for pulling together these updates.
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 if you intend to be available during the meeting for discussion or if you will be async.
You must be logged in to post a comment.