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.
WordPress 6.4 Beta 1 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed to getting this to 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 and those who came and led the release party on September 26.
WordPress Performance team has a new version of the Performant TranslationspluginPluginA 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 with improved compatibility and performance. It has more than 1000 installations as at September 26, 2023. More testers will be needed and @swissspidy has created a proof-of-concept core patch in the meantime.
Forthcoming release updates
Next major WordPress release: 6.4
WordPress 6.4 Beta 2 is scheduled for October 3, 2023.
Project Board for Editor Tasks for WordPress 6.4 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/
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/
Gutenberg 16.7 due to go live on September 27, 2023
Tickets or Components help requests
Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticketCreated for both bug reports and feature development on the bug tracker. if needed.
Open floor
If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.
WordPress 6.4 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 is September 26, 2023today
@flixos90 committed [56681] and just opened a follow up bug fix PR that would be great to commit in the next hour if there is consensus (since committed in [56717])
@mukesh27 has been working on additional unit tests for #22192
@joemcgill posted some additional benchmarking for the two approaches in flight for #57789, and plans to do some more profiles to get more detailed info on both. He is still planning on tracking these PRs in 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/ repos but have punted to 6.5 for now to keep the release moving while this is getting worked out.
@pbearne would like to start working/focus on the option auto-loading issue. now that there is the new 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. to allow easy shortcutting from [55256]
@flixos90: There are a few more existing ideas around, some of which are being worked on already, such as #42441
For any new ideas, a good next step would be to open issues. Depending on what you envision, you may either want to open a new TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker. or a new module proposal in the 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
There’s also the autoloaded options Site Health check in Performance Lab, for which there are a few ideas to make it more helpful
JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. & CSSCSSCascading Style Sheets.
@westonruter committed elimination of manual construction of script tags in WP_Scripts and of inline scripts on frontend/login screen in [56687] (see #58664). With this, Strict CSP can now be opted into on the frontend and wp-login screen. Followed up on prior ticket which sought to do the same for all of WP, and opened new ticket to complete effort in admin.
@westonruter also iterated on PR for #55491. In 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. scrub yesterday, we agreed this ticket is actually a defect and not an enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature., so it can still land after beta1 today
@pereirinha could use some help to track the tickets that need help
@flixos90: One of the most flexible ways to search Trac with various filters is the https://core.trac.wordpress.org/queryURLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org
For example, this query shows all remaining 6.4 tickets with a performance focus; it looks like most tickets there are already assigned but please feel free to take a closer look and familiarize yourself with those issues to see if you’re interested in a particular ticket and/or have additional feedback
@10upsimon pretty much finalized https://github.com/WordPress/performance/issues/651, has implemented necessary logic for redirection back to WPP Settings Screen following certain standalone plug-in actions, will outline in code review given that a few approaches needed to be tested before arriving at the working solution.
@flixos90 is looking forward to taking a closer look
There was consensus that due to a lack of feedback this should be punted to the 6.5 milestone
Let’s continue discussing on the ticket so we can figure out a good approach for 6.5
@thekt12 has updated the PR for #59442 and would like additional feedback since he is not confident if this leads to any new issue as the new approach does change how cache key is generated for query
WordPress 6.4 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 will be released in less than a week on September 26th. The full development cycle for 6.4 can be found here: https://make.wordpress.org/core/6-4/
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/ 16.7 RC1 was released right before the meeting. It’s available to test through GitHub.
@mdxfr shared several regressions related to the post excerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. functionality in WordPress 6.3.
About Cover 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. align-top doesn’t work for awareness, the fix was merged into 16.7, thx (https://github.com/WordPress/gutenberg/pull/54050), maybe we can pick it into WP6.3.2 target list also…
@proxxim asked about any plans for adding a focal point picker to the cover block when it pulls in the 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. of a post. We moved the discussion to the relevant GitHub issue.
Once again it’s time to submit your proposals, as Interop 2024 is happening! WordPress developers, please contribute your proposals for 2024 as on GitHub or as a comment on this post.
What is Interop?
Developing for the web’s diverse browsers has historically been complicated by gaps in browser capabilities that developers had to work around. Interop is a multi-year, multi-browser effort to address that.
Interop aims to improve interoperability across the three major web browser engines (Chromium, WebKit and Gecko) in important areas as identified by web developers. Interop provides a benchmark – agreed on by representatives of three major browsers and developed through a process of public nomination – and a scoring mechanism. The overall goal is to make developers’ lives better by enabling a widely compatible “Baseline” of web platform features.
The scale of WordPress and the wide variety of use cases we support puts WordPress developers in a unique position to contribute to and benefit from this effort. In the past, WordPress has helped identify and adopt important features like `srcset` and native lazy loading, and Interop gives us an opportunity to contribute feedback directly to browser developers.
The Interop 2023 work has already made great progress including on suggestions WordPress developers made on last year’s post like color-mix, inert, import-maps and some contentEditable areas. Now, the effort has begun to identify issues for Interop 2024.
What browser interoperability issues continue to present problems for WordPress developers? You can make suggestions to the Interop 2024 project directly by opening a GitHub issue or leave a detailed comment below.
Suggestions can include features that have inconsistent behaviors across browsers or features that aren’t available in all browsers. When formulating proposals, keep in mind that the goal of the project is to improve interoperability between browsers rather than identify new features.
What potential features in WordPress are blocked by cross-browser compatibility issues? Help make browsers better by submitting issues!
Analysing the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. web vitals performance impact of WordPress 6.3 in the field
The FSE Outreach Program will become a focused space for solving issues, creating resources, and facilitating conversations around Phase 2 adoption. You can contribute by commenting on this post.
After 6.4 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, the facilitated calls for FSE testing will be replaced by ad hoc calls for testing run by the Make Test team or contributors who need specific features tested.
Project Board for Editor Tasks for WordPress 6.4 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/
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/
Reminder of revised schedule:
Gutenberg 16.7 RC1 on September 20, 2023 (originally planned on September 13)
Gutenberg 16.7 on September 27, 2023
Tickets or Components help requests
Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticketCreated for both bug reports and feature development on the bug tracker. if needed.
Request from 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. scrubs from @joedolson to get some testing on the following tickets: #50846, and #58912
Open floor
If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.
WordPress 6.4 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 is September 27, 2023
@mukesh27 I’ve been working on issue #22192 and have received some feedback related to backward compatibility on the PR. I’m now in need of feedback from Joe and Felix
@thekt12#58196 in progress, planning to give for initial review tomorrow
@joemcgill I made good progress on #57789 yesterday and could use a second set of eyes. It doesn’t full solve the issue of making Theme.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. data persistent, but is a step in that direction, which reduces unnecessary recalculation of that data during a page load. I’m going to work on a parallel PR to 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/ repo to get some testing of the strategy in the 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 prior to making the change in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
@spacedmonkey It is unclear of the path forward of #59188 there seems to be disagreement on best path forward
@mukesh27 The majority of the work from my end has already been committed for the 6.4 milestone. I am now providing support to Jonny for the review and testing process.
JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. & CSSCSSCascading Style Sheets.
@westonruter Similarly, I have the elimination of manual script 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.) construction scope reduced to not include the adminadmin(and super admin). Now it is just the frontend and the login screen. PR ready for review. https://github.com/WordPress/wordpress-develop/pull/4773
@flixos90 Otherwise, reviewing the PRs for #58892 and #58893 which I see have received updates since, so I’ll take another look shortly after this chat
@flixos90 Last week I spent some time conducting field analyses to assess the performance impact of the WordPress 6.3 release. Primarily focusing on Web Vitals metric LCP which measures load time performance, and how it’s affected both in general, but also specifically by the two major enhancements that were projected to affect LCP:
the emoji loader script optimizations
the lazy-loading plus fetchpriority improvements
Sharing the most important highlights:
Overall, the Largest Contentful Paint (LCP) passing rate has improved by 5.6% for classic theme sites and by 2.7% for 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. theme sites
The Largest Contentful Paint (LCP) boost for classic theme sites using the emoji loader script is 3.4% to 7% higher than for those that don’t use it, and for block themes it’s 0.7% to 4.5% better as well
When looking at only the sites where that is the case and which were still lazy-loading the LCP image with WordPress 6.2, the LCP performance impact amounts to a massive 16% to 21% improvement for mobile viewports and 6% to 9% on desktop.
Lazy-loading accuracy has notably improved: In WordPress 6.3, only 9-10% of sites still lazy-load their LCP image for classic theme sites (down from 27-28% in 6.2) while for block theme sites it’s 5-8% (down from 17-29% in 6.2)
@joemcgill I wanted to mention that we should probably prepare some time after beta1 next week for some initial triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of any performance issues we see after the first round of code syncing from the Gutenberg project has occurred.
@spacedmonkey I would like to start a tracking ticket for dev notesdev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. this team is going to work on
Created https://github.com/WordPress/performance/issues/840 for tracking 6.4 Trac tickets that require dev notes
Here is the agenda for this week’s performance team meeting scheduled for Sep 19, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.
WordPress 6.4 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 is September 27, 2023
At a high level, we will go through quick intros (what each person does/focuses on) before reviewing WordPress 6.3 performance impact in the field, diving into WordPress 6.4 performance improvements and looking ahead at what can be learned for WordPress 6.5.
As a reminder, hallway hangouts are meant to be casual and collaborative so come prepared with a kind, curious mind along with any questions or items you want to discuss around this important area of the project, especially since the agenda is intentionally loose to allow for it.
I’ve been working on refactoring how the block toolbar is semantically communicated in the DOM by moving it to render in the editor 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., rather than within the editor canvas.
The is a PR as a proof of concept. It is not ready to really be reviewed but is useful for seeing the direction it’s going
Registering Variations for Posts terms and Nav 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.
@gaambo mentioned two issues they’d wish for some feedback and/or help with:
