Title: 6-3 – Make WordPress Core --- # Tag Archives: 6-3 [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 11:44 pm _on_ October 18, 2023 Tags: 6-3, [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 899 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 966 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat Summary, October 18, 2023](https://make.wordpress.org/core/2023/10/18/dev-chat-summary-october-18-2023/)󠁿 The WordPress Developers Chat meeting took place on [October 18, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231018T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1692216005854449) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/). ## Announcements * [WordPress 6.4 Release Candidate 1](https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-1/): Download the latest 6.4 build and don’t forget [this handy reference guide](https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/) for testing the latest features. ## Highlighted Posts * [WordPress 6.4 Release Candidate Phase](https://make.wordpress.org/core/2023/10/17/wordpress-6-4-release-candidate-phase/): Learn or refresh your knowledge of what happens during RCrelease candidate One 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)](https://make.wordpress.org/core/tag/6-3/?output_format=md#alpha-beta).. Questions? Please post them in [the comments](https://make.wordpress.org/core/2023/10/17/wordpress-6-4-release-candidate-phase/). * [6.4 Dev Notes](https://make.wordpress.org/core/tag/dev-notes-6-4/): It’s been a busy time in the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)! Stay updated on the latest technical updates by checking out posts conveniently tagged with [#dev-notes-6-4](https://make.wordpress.org/core/tag/dev-notes-6-4/). _Major props_ to dev notedev note Each 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. authors and wranglers who have worked tirelessly to make this happen! 🎉 * [WordPress core is now using Playwright for all browser-based tests](https://make.wordpress.org/core/2023/10/16/wordpress-core-is-now-using-playwright-for-all-browser-based-tests/): e2e fans rejoice! This milestone promises improved test stability and better options for authoring tests. If you’ve been holding back while the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. from Puppeteer to Playwright has been underway, now is a great time to jump back in to improve Core e2e coverage. * [What’s new in Gutenberg 16.8 (11 October)](https://make.wordpress.org/core/2023/10/11/whats-new-in-gutenberg-16-8-11-october/): Check out updates to the Cover blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., Font Library, and more in this roundup of the latest release. ## Release Updates ### WordPress 6.4 **RC 2 is scheduled for next Tuesday, October 24, 2023.** Stay in the loopLoop The 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](https://codex.wordpress.org/The_Loop) with 6.4 by following: * [WordPress 6.4 Development Cycle](https://make.wordpress.org/core/6-4/) * [Roadmap to 6.4](https://make.wordpress.org/core/2023/08/22/roadmap-to-6-4/) — this next major releasemajor release A 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. is scheduled for November 7, 2023 * [Testing WordPress 6.4](https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/)— a detailed guide for testing new and refined features * [6.4 Editor tasks board](https://github.com/orgs/WordPress/projects/127) * [Release parties schedule for 6.4](https://make.wordpress.org/core/2023/08/29/6-4-release-parties-schedule-and-hosts/) * [Bug Scrub Schedule 6.4](https://make.wordpress.org/core/2023/08/17/bug-scrub-schedule-for-wordpress-6-4/) ✅ (current schedule is complete) * and following along in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel Additional release updates from the floor included: * [A question was raised](https://wordpress.slack.com/archives/C055Y7FKS7N/p1697651668430749) in [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) about removing some GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)- only packages from the next npm package update to Core. * Some 6.4 dev notesdev note Each 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. drafts are still needed for a couple of areas, so [a gentle reminder was raised](https://wordpress.slack.com/archives/C02RQBWTW/p1697660898273199) to keep the official [6.4 Documentation Tracker](https://github.com/orgs/WordPress/projects/141) updated with latest progress. Reach out on the Tracker for help or to the Documentation release group in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel. ## WordPress 6.3.2 * [WordPress 6.3.2 – Maintenance and Security release](https://wordpress.org/news/2023/10/wordpress-6-3-2-maintenance-and-security-release/): This follow-up to 6.3.1 introduces several bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions( adverse changes from the previous version) being the highest priority. fixes and security updates. Make sure to update! * Keep tabs on the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel for future updates. ## Open Floor ### Automated Welcome/Signposting for 󠀁[#core](https://wordpress.slack.com/archives/C02RQBWTW)󠁿 [@webcommsat](https://profiles.wordpress.org/webcommsat/) [asked](https://wordpress.slack.com/archives/C02RQBWTW/p1697661423730869) if Core would consider utilizing an automated messaging/workflow tool similar to that used by Training. When users joined the channel, they would receive a private message from Slackbot that includes channel-specific info and links, such as the Dev Chat schedule, or orientation for new contributors and contributor days. Abha agreed to draft a proposal to seek broader input from Core and new contributors. ### Use of `noopener noreferrer` in New Window/Tab Links [@presskopp](https://profiles.wordpress.org/presskopp/) [had a question](https://wordpress.slack.com/archives/C02RQBWTW/p1697661466210439) regarding use of `rel="noopener noreferrer"` in links with `target="_blank"`, which were [supposed to have been removed](https://core.trac.wordpress.org/ticket/49558). To help resolve instances where this unneeded behavior remains (in Core and Gutenberg), contribute to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. [#53843: Remove adding of rel=”noopener” to links with target=”_blank”](https://core.trac.wordpress.org/ticket/53843). ## Next Meeting The next meeting will be on [October 25, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231025T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props _[@webcommsat](https://profiles.wordpress.org/webcommsat/)_ for peer review of this post._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 10:53 pm _on_ October 11, 2023 Tags: 6-3, [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 899 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 966 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat summary, October 11, 2023](https://make.wordpress.org/core/2023/10/11/dev-chat-summary-october-11-2023/)󠁿 Summary of the WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel. ## Key links [Start of the Dev Chat meeting on the Core Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1697054420957149) [Dev Chat agenda](https://make.wordpress.org/core/2023/10/11/dev-chat-agenda-october-4-2023-2/) followed – thanks to [@webcommsat](https://profiles.wordpress.org/webcommsat/) for preparing. ## **Announcements** * [WordPress 6.4 Beta 3 is available](https://wordpress.org/news/2023/10/wordpress-6-4-beta-3/): Please help test and make the release the best it can be! Thanks to everyone who contributed toward BetaBeta A 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. 3, as well as those who came and facilitated the release party on October 10. Note the [Twenty Twenty Four images issue](https://core.trac.wordpress.org/ticket/59526) has been resolved, and the images are rendering correctly in Beta 3. * The WordPress 6.3.2 minor releaseMinor Release A 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. has moved to tomorrow,** October 12, 2023** (more information under release updates to follow). ## **Highlighted Posts** * [Four Weeks in Core](https://make.wordpress.org/core/2023/10/10/a-week-in-core-october-9-2023/): Many thanks to [@audrasjb](https://profiles.wordpress.org/audrasjb/) for this update covering the amazing activity in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 4 and October 9, 2023: - 269 commits - 337 contributors - 295 tickets created - 43 tickets reopened - 277 tickets closed * [Core Editor Improvement: Ensuring Excellence in the Writing Experience](https://make.wordpress.org/core/2023/10/05/core-editor-improvement-ensuring-excellence-in-the-writing-experience/): Check out some of [6.4’s editor improvements](https://github.com/WordPress/gutenberg/issues/53305), including new keyboard shortcuts, smoother list merging, and more. This post also includes a video demonstrating some of these enhancements. As you test these updates, [please report bugs or suggestions](https://github.com/WordPress/gutenberg/issues). Thanks to [@annezazu](https://profiles.wordpress.org/annezazu/) 🙏🏻 * Reminder: [Hallway Hangout: Working session on consolidating various navigation modes](https://make.wordpress.org/core/2023/10/02/hallway-hangout-working-session-consolidating-modes/): Taking place on November 15, 2023 at 16:00 UTC. This is part of efforts to improve accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” ( i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia. org/wiki/Accessibility) in the Site Editor. * The [Dev Blog](https://developer.wordpress.org/news/) is looking for a writer for the following topic: [How to add commands to the command palette](https://github.com/WordPress/developer-blog-content/discussions/157). Please respond on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) ticketticket Created for both bug reports and feature development on the bug tracker. if you are interested. ## **Release Updates** ### Next major releasemajor release A 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.4 **Release Candidaterelease candidate One 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)](https://make.wordpress.org/core/tag/6-3/?output_format=md#alpha-beta). 1 is scheduled for next Tuesday, October 17, 2023.**  This hallway hangout is happening tomorrow, October 12, 2023: [What’s new for developers in WordPress 6.4](https://www.meetup.com/learn-wordpress-online-workshops/events/296105065/). Stay in the loopLoop The 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](https://codex.wordpress.org/The_Loop) with 6.4 by following: * [WordPress 6.4 Development Cycle](https://make.wordpress.org/core/6-4/) * [Roadmap to 6.4](https://make.wordpress.org/core/2023/08/22/roadmap-to-6-4/) — this next major release is scheduled for November 7, 2023 * [Testing WordPress 6.4](https://make.wordpress.org/test/2023/09/26/help-test-wordpress-6-4/)— a detailed guide for testing new and refined features * [6.4 Editor tasks board](https://github.com/orgs/WordPress/projects/127) * [Release parties schedule for 6.4](https://make.wordpress.org/core/2023/08/29/6-4-release-parties-schedule-and-hosts/) * [Bug Scrub Schedule 6.4](https://make.wordpress.org/core/2023/08/17/bug-scrub-schedule-for-wordpress-6-4/) * and following along in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel ### 6.4 tickets that need attention [@rajinsharwar](https://profiles.wordpress.org/rajinsharwar/) highlighted [#52529](https://core.trac.wordpress.org/ticket/52529) and requested testing of the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. to see if they can replicate the errors mentioned. ### **Dev Notesdev note Each 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.** [@webcommsat](https://profiles.wordpress.org/webcommsat/) for the release documentation group: A reminder that the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/). The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is due to be published next week. This is so the link can be included in the release’s About Page. It would be great to have as many dev notes ready in draft as soon as possible, so they can have a final review and be published. [6.4 dev notes tracking project board](https://github.com/orgs/WordPress/projects/141) for reviews and publishing is in progress. **GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)**– Some Gutenberg tickets have already been labelled and clustered. There is a significant list that is being clustered and labelled, and these will then get added to the  [documentation tracker for 6.4](https://github.com/orgs/WordPress/projects/141). The tracker will show the edit, review and publish status of the dev notes – the view that will be most useful for this is ‘dev notes’. For Gutenberg, the wrangling and discussion on clustering and inclusions will happen in the Gutenberg tracker. Thanks to [@bph](https://profiles.wordpress.org/bph/) who is going to be helping with this. **Core** – If you are a component maintainer, and have not already shared that you are working on a dev notedev note Each 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. relating to a Core Trac ticket or cluster of tickets, please add a comment on [this issue](https://github.com/WordPress/Documentation-Issue-Tracker/issues/1148) and link any google docs, and we will populate the tracker with this. **For End user and Core tickets**, the labelling is continuing. As we are being advised of dev notes needed or in progress by maintainers, they are being added to the documentation tracker. **For performance dev notes**, issues are being added to the documentation tracker once confirmed for reviews and publishing purposes. Wrangling and discussion of inclusion of tickets is happening on the [Performance GitHub ticket](https://github.com/WordPress/performance/issues/840). **Reviews **– If any devs are able to assist with technical reviews of dev notes if needed, let [@webcommsat](https://profiles.wordpress.org/webcommsat/) know to update the list. ### Next minor release: 6.3.2 * [WordPress 6.3.2 RC1 is available](https://make.wordpress.org/core/2023/10/06/wordpress-6-3-2-rc1-is-now-available/): Please join in to help test! * ***A note on the 6.3.2 release schedule change:*** In order to accommodate the need for hosts to deal with an important [curl 8.4.0 security release](https://github.com/curl/curl/discussions/12026) on Wednesday, the 6.3.2 final release has been moved to Thursday, October 12, 2023. * Follow the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel for the latest updates. * Thanks to everyone who led, supported, helped test, raised issues, and helped to fix tickets in these releases!  ### Gutenberg [Gutenberg 16.8.0](https://wordpress.org/plugins/gutenberg/) shipped during dev chat. An update on this release will be published soon and will be findable on the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) on the Make/ Core blogblog (versus network, site). ## **Component Maintainers **requests [@rajinsharwar](https://profiles.wordpress.org/rajinsharwar/) highlighted Trac ticket [#55335](https://core.trac.wordpress.org/ticket/55335). Requested confirmation if it should be considered a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.. ## Open floor No additional items were raised. A reminder of the Field Guide and dev notes was shared. Props to [@webcommsat](https://profiles.wordpress.org/webcommsat/) for the agenda and summary, and to [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) for facilitating the meeting and reviewing the summary. [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 3:05 pm _on_ October 6, 2023 Tags: 6-3, [minor releases ( 38 )](https://make.wordpress.org/core/tag/minor-releases/), [releases ( 56 )](https://make.wordpress.org/core/tag/releases/)    # 󠀁[WordPress 6.3.2 RC1 is now available](https://make.wordpress.org/core/2023/10/06/wordpress-6-3-2-rc1-is-now-available/)󠁿 **Update (Oct. 9):** In order to accommodate the need for hosts to deal with the pending [curl 8.4.0 security release](https://github.com/curl/curl/discussions/12026) on Wednesday, the 6.3.2 final release date will be delayed to Thursday, Oct 12. WordPress 6.3.2 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release: * Use the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. - As this is a minor RCrelease candidate One 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)](https://make.wordpress.org/core/tag/6-3/?output_format=md#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](https://make.wordpress.org/core/handbook/contribute/codebase/). * Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) to test: `wp core update `[https://wordpress.org/wordpress-6.3.2-RC1.zip](https://wordpress.org/wordpress-6.3.2-RC1.zip) * [Directly download the Beta/RC version](https://wordpress.org/wordpress-6.3.1-RC1.zip). ## What’s in this release candidate? 6.3.2 RC1 features [19 fixes on Core](https://core.trac.wordpress.org/query?status=closed&milestone=6.3.2&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=priority) as well as [22 fixes](https://core.trac.wordpress.org/ticket/59293) for the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor. The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed: * [#59489](https://core.trac.wordpress.org/ticket/59489) — Themes: Fix core block style paths on Windows * [#59198](https://core.trac.wordpress.org/ticket/59198) — Upgrade/Install: Check plugin compatibility during bulk upgrades * [#59293](https://core.trac.wordpress.org/ticket/59293) — Editor: Update packages with bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes for 6.3.2  * [#59086](https://core.trac.wordpress.org/ticket/59086) — Twenty Twenty: Fix style issues within iframed editor * [#59196](https://core.trac.wordpress.org/ticket/59196) — Build Tools: Avoid doing` copy:dynamic` when running `grunt watch` when using `--dev` option * [#59193](https://core.trac.wordpress.org/ticket/59193) — REST APIREST API The 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/](https://developer.wordpress.org/rest-api/): Remove misleading comment in `WP_REST_Blocks_Controller->get_item_schema` * [#59108](https://core.trac.wordpress.org/ticket/59108) — Editor: Preserve block style variations when securing theme * [#59041](https://core.trac.wordpress.org/ticket/59041) — Post Types: allow trashing draft patterns * [#59018](https://core.trac.wordpress.org/ticket/59018) — Editor: Fix loading of assets in blocks in child themes where the directory name starts with the parent theme’s directory name * [#59000](https://core.trac.wordpress.org/ticket/59000) — Editor: Prevent possibility of a fatal error when previewing block themes * [#58754](https://core.trac.wordpress.org/ticket/58754) — Editor: Don’t use fluid layout value in typography * [#58119](https://core.trac.wordpress.org/ticket/58119) — HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: Remove all duplicate copies of an attribute when removing * [#59394](https://core.trac.wordpress.org/ticket/59394) — Build/Test Tools: Add` sys_get_temp_dir()` to `open_basedir` tests * [#59320](https://core.trac.wordpress.org/ticket/59320) — Upgrade/Install: Fix broken `sprintf()` call when deleting a backup * [#59292](https://core.trac.wordpress.org/ticket/59292) — HTML API: Skip over contents of RAWTEXT elements such as STYLE * [#58779](https://core.trac.wordpress.org/ticket/58779) — Build/Test Tools: Restore automatically retrying failed E2E tests once * [#59111](https://core.trac.wordpress.org/ticket/59111) — Themes: Avoid stale caches for core block styles * [#59226](https://core.trac.wordpress.org/ticket/59226) — Posts, Post Types: Reinstate missing sort_column options in get_pages() * [#59224](https://core.trac.wordpress.org/ticket/59224) — Posts, Post Types: Avoid redundant SQL query in get_pages() The following block editor issues from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) are fixed: * [Global Styles: Fix push to global styles for 6.3.x](https://github.com/WordPress/gutenberg/pull/53624) * [Footnotes: enlarge rich text footnote target](https://github.com/WordPress/gutenberg/pull/54119) * [Fallback to default max viewport if layout wide size is fluid.](https://github.com/WordPress/gutenberg/pull/53551) * [Site editor: add missing i18n in HomeTemplateDetails](https://github.com/WordPress/gutenberg/pull/53543) * [RichText: Remove ‘Footnotes’ when interactive formatting is disabled](https://github.com/WordPress/gutenberg/pull/53474) * [Preserve block style variations when securing theme json](https://github.com/WordPress/gutenberg/pull/53466) * [Image: Clear aspect ratio when wide aligned](https://github.com/WordPress/gutenberg/pull/53439) * [Fix missing Replace button in content-locked Image blocks](https://github.com/WordPress/gutenberg/pull/53410) * [Remove “go to” for terms and posts](https://github.com/WordPress/gutenberg/pull/53408) * [Image block: Fix stretched images constrained by max-width](https://github.com/WordPress/gutenberg/pull/53274) * [Fix: Sync status overlaps for some languages in Patterns post type page](https://github.com/WordPress/gutenberg/pull/53243) * [Fix document title alignment in command palette button](https://github.com/WordPress/gutenberg/pull/53224) * [Update document title buttons radius](https://github.com/WordPress/gutenberg/pull/53221) * [Fix: Snack bar not fixed on certain pages in the Site Editor](https://github.com/WordPress/gutenberg/pull/53207) * [Image Block: Don’t render DimensionsTool if it is not resizable ](https://github.com/WordPress/gutenberg/pull/53181) * [Site Editor: Fix document actions label helper method](https://github.com/WordPress/gutenberg/pull/52974) * [Add tests for fluid layout + typograph](https://github.com/WordPress/gutenberg/pull/53554) * [Fix support of sticky position in non-iframed post editor](https://github.com/WordPress/gutenberg/pull/53540) * [Link Control: persist advanced settings toggle state to preferences if available](https://github.com/WordPress/gutenberg/pull/52799) * [Fix: indicator style when block moving mode](https://github.com/WordPress/gutenberg/pull/53972) * [Fix post editor top toolbar with custom fields in Safari](https://github.com/WordPress/gutenberg/pull/53688) * [Set top toolbar size dynamically](https://github.com/WordPress/gutenberg/pull/53526) ## What’s next? The `dev-reviewed` workflow ([double committer sign-off](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-beta-versions/#double-committer-signoff)) is now in effect when making changes to the 6.3 branchbranch A 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 ~Wednesday, October 11th, 2023~ Thursday, October 12th, 2023. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel. A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test! The WordPress 6.3.2 first release candidaterelease candidate One 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)](https://make.wordpress.org/core/tag/6-3/?output_format=md#alpha-beta). was led by [@joemcgill](https://profiles.wordpress.org/joemcgill/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/) with the help of [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) at mission control and [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) on Editor backports. [#6-3](https://make.wordpress.org/core/tag/6-3/), [#minor-releases](https://make.wordpress.org/core/tag/minor-releases/), [#releases](https://make.wordpress.org/core/tag/releases/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 9:00 pm _on_ September 22, 2023 Tags: 6-3, [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 899 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 966 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat Summary, September 20, 2023](https://make.wordpress.org/core/2023/09/22/dev-chat-summary-september-20-2023/)󠁿 The notes from the weekly WordPress developers chat which took place on [September 20, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230920T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Dev Chat agenda](https://make.wordpress.org/core/2023/09/20/dev-chat-agenda-september-13-2023-2/) and highlighted posts followed for the meeting, prepared by [@webcommsat](https://profiles.wordpress.org/webcommsat/) * [Start of the meeting on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1695240004988449) hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) ## Announcements No announcements were made this week. ## Highlighted Posts [**Hallway Hangout: Performance Improvements for WordPress 6.4**](https://make.wordpress.org/core/2023/09/18/hallway-hangout-performance-improvements-for-wordpress-6-4/): Make plans to talk Performance at this hangouts session planned for [October 19, 2023 at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231019T1500). [**Analyzing the Core Web Vitals performance impact of WordPress 6.3 in the field**](https://make.wordpress.org/core/2023/09/19/analyzing-the-core-web-vitals-performance-impact-of-wordpress-6-3-in-the-field/): Read this thorough breakdown from @felixarntz of how 6.3 performance improvements have been reflected on production sites using WordPress at scale. Feedback in invited on the post. [**Community Summit Discussion Notes: Increasing contributor recognition and celebration**](https://make.wordpress.org/summit/2023/09/15/community-summit-discussion-notes-increasing-contributor-recognition-and-celebration/): Join the discussion on how contributor impact can be better identified and highlighted. The discussion at the summit considered the system of props, credit outside of a release, badges, encouragement of contribution. [**Evolving the FSE Outreach Program**](https://make.wordpress.org/core/2023/09/07/evolving-the-fse-outreach-program/): A reminder to provide feedback on the next phase for the [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00): Deadline for feedback: Friday, September 22, 2023 Additional Highlighted Post on Interoperability under Open Floor. ## Release Updates #### Next major WordPress release: 6.4 The last bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub before BetaBeta A 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 on [Monday, September 25, 2023 at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230925T1700). More on 6.4 highlighted under Open Floor. **Beta 1 is scheduled for next Tuesday, September 26.** Stay in the loopLoop The 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](https://codex.wordpress.org/The_Loop) with 6.4 by following: * [Release parties schedule for 6.4](https://make.wordpress.org/core/2023/08/29/6-4-release-parties-schedule-and-hosts/) * [WordPress 6.4 Development Cycle](https://make.wordpress.org/core/6-4/) * [6.4 Editor tasks board](https://github.com/orgs/WordPress/projects/127) * [Roadmap to 6.4](https://make.wordpress.org/core/2023/08/22/roadmap-to-6-4/) – this next major releasemajor release A 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. is scheduled for November 7, 2023 * [Bug Scrub Schedule 6.4](https://make.wordpress.org/core/2023/08/17/bug-scrub-schedule-for-wordpress-6-4/). The scrubs take place in the [core](https://wordpress.slack.com/archives/C02RQBWTW) channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). * and following along in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel ## GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. 󠀁[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)󠁿 Reminder: the revised release schedule for the next Gutenberg release is as follows: * [Gutenberg 16.7 RC1](https://github.com/WordPress/gutenberg/releases/tag/v16.7.0-rc.1): released September 20 (originally planned for September 13) * Gutenberg 16.7: September 27 ## Components & Tickets Testing request following a recent bug scrub from [@joedolson](https://profiles.wordpress.org/joedolson/): * TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. [#58912](https://core.trac.wordpress.org/ticket/58912): Mobile: Adminadmin (and super admin) menu unexpectedly closes with Safari – after the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. is updated, this will be ready for testing * Trac ticket [#58756](https://core.trac.wordpress.org/ticket/58756): Media library improvements: UIUI User interface, Non-closing options, and Button select state issues in image editing – this is ready for testing * Trac ticket [#40822](https://core.trac.wordpress.org/ticket/40822): no longer requires further feedback and is ready for commit From the tickets posted by [@oglekler](https://profiles.wordpress.org/oglekler/) before dev chat, assistance is needed with the [list of tickets left to tackle before Beta 1](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&type=enhancement&type=feature+request&component=!Build%2FTest+Tools&keywords=~-gutenberg-merge+-commit+-close&milestone=6.4&col=id&col=summary&col=type&col=status&col=milestone&col=component&col=owner&col=priority&col=changetime&order=changetime)( updated September 22, 2023): * Trac [#55459](https://core.trac.wordpress.org/ticket/55459): Change Login Label name * Trac [#56886](https://core.trac.wordpress.org/ticket/56886): Admin facing add site screen missing search engine visibility field * Trac [#58703](https://core.trac.wordpress.org/ticket/58703): wp-list-table: < label> is preceding in the checkbox column – this ticket has a new patch, and further testing is requested * Trac [#40762](https://core.trac.wordpress.org/ticket/40762): Login: add canonical admin shorthand URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for login.php ## Open Floor * **Call for WordPress developer proposals: **Update from [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) regarding Interop 2024 was added to the Highlighted Posts list by [@webcommsat](https://profiles.wordpress.org/webcommsat/). [Seeking proposals for Interop 2024](https://make.wordpress.org/core/2023/09/20/seeking-proposals-for-interop-2024/). WordPress developers are asked to contribute their proposals for 2024 as [on GitHub](https://github.com/web-platform-tests/interop/issues/new/choose) or as a comment on the proposals post. Interop aims to improve interoperability across the three major web browser engines (Chromium, WebKit and Gecko) in important areas as identified by web developers. * **Call for assistance with 6.3.2: **[@joemcgill](https://profiles.wordpress.org/joemcgill/) highlighted [@mikeschroder](https://profiles.wordpress.org/mikeschroder/)‘s message about next steps for getting another bugfix out for 6.3, and if there were any contributors available to help lead the release. - [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) raised that there may be many busy with beta 1 next week, and more hands may be raised after this - [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) thought the concern before WCUS was that something(s) milestoned for 6.3.2 might be worth getting out before 6.4 lands. He asked if people had interest and availability, could they share this in the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) Slack channel as it would be very helpful. > * ** A number of contributors highlighted the final stretch to 6.4 Beta 1, and > the calls to help deal with as many bugs as possible, clear triagetriage The > act of evaluating and sorting bug reports, in order to decide priority, severity, > and other factors. queues, and review available content. > @cbringmann reminded > the meeting that contributions are for all and not restricted to just the release > squad and cohort. She thanked everyone who is lending a hand to the 6.4 release. ## Next Meeting The next meeting will be on [Wednesday September 27, 2023, at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230927T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). Props to [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/) for hosting the meeting, [@webcommsat](https://profiles.wordpress.org/webcommsat/) and [@zunaid321](https://profiles.wordpress.org/zunaid321/) for the notes, and to [@marybaum](https://profiles.wordpress.org/marybaum/) and [@oglekler](https://profiles.wordpress.org/oglekler/) for reviews and updates on tickets. [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/flixos90/) [Felix Arntz](https://profiles.wordpress.org/flixos90/) 7:56 pm _on_ September 19, 2023 Tags: 6-3, [analysis ( 3 )](https://make.wordpress.org/core/tag/analysis/), [performance ( 404 )](https://make.wordpress.org/core/tag/performance/), [summary ( 966 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Analyzing the Core Web Vitals performance impact of WordPress 6.3 in the field](https://make.wordpress.org/core/2023/09/19/analyzing-the-core-web-vitals-performance-impact-of-wordpress-6-3-in-the-field/)󠁿 As highlighted in the [WordPress 6.3 performance summary post](https://make.wordpress.org/core/2023/08/07/wordpress-6-3-performance-improvements/), the 6.3 release included numerous performance enhancements. Based on the lab benchmarks cited in that post, the test sites used with WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. were loading 27% faster for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes and 18% faster for classic themes based on the [Largest Contentful Paint (LCP) metric](https://web.dev/lcp/). While lab benchmarks are great to estimate the projected performance impact of a release, the tests are not representative of the average WordPress site and real- world traffic. Therefore, it is crucial to further review and attempt to validate the impact in the field, i.e. on actual production sites using WordPress, at scale. Last week, three analyses were conducted to assess the performance impact of WordPress 6.3, using the public data sets from [HTTP Archive](https://httparchive.org/) and the [Chrome User Experience Report](https://developer.chrome.com/docs/crux/). ## Highlights of the WordPress 6.3 performance analysis findings Before diving into the results, the term “passing rate” should be briefly explained here. It denotes the percentage of sites in a dataset for which a specific Web Vitals metric performs better than the threshold value that is considered “good”. For LCP, that encompasses all sites in the dataset that load faster than 2.5 seconds in total per the LCP metric. For example, if 600,000 out of 1,000,000 URLs have an LCP faster or equal to 2.5 seconds, the LCP passing rate is 60%. The results from the analyses indicate that WordPress 6.3 is indeed a great success from a performance perspective, as indicated by the lab benchmarks. Some notable findings to highlight include: * Looking at all applicable sites in the dataset, the **Largest Contentful Paint( LCP) passing rate has improved by 5.6% for classic theme sites and by 2.7% for block theme sites** for mobile viewports. In terms of the absolute LCP passing rate, for classic theme sites this means a bump from 31.3% to 33%, while for block theme sites it means a bump from 42.8% to 44%. For desktop viewports, the improvements are not as pronounced, yet they are still positive. See the [source for overall LCP passing rate changes](https://colab.research.google.com/drive/1-mrV_JOt93BqL8WahdBwhexbAExXGHMd#scrollTo=2a4t0e7GnN4g). * When segmenting between sites that use the emoji loader script and the sites that have disabled it, the impact of the improvements to the emoji loader script are clearly visible. 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. To outline the numbers behind that more clearly, classic theme sites using the emoji loader script see a relative LCP boost of 8.4% on phone and 2.4% on desktop, compared to only 1.4% and -0.8% for those that _don’t_ use the emoji loader script. Similarly, for block theme sites using the emoji loader script the relative LCP boost amounts to 4.2% on phone and 0.8% on desktop, compared to only -0.3% and 0.1% for those that _don’t_ use the emoji loader script. See the [source for LCP passing rate differences between sites using vs not using the emoji loader script](https://colab.research.google.com/drive/1KY0rbwYsubZSa3uI9Lu-P2n2UlJo_y0C#scrollTo=LeMIDj8V5PHD). * When looking at the impact of more accurate lazy-loading heuristics and support for `fetchpriority="high"`, segmentation is especially important, since the enhancements themselves have a varying degree of accuracy. As a reminder, the LCP image of a URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org should _not_ be lazy-loaded, but it _should_ have `fetchpriority="high"`. **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.** Even in absolute LCP passing rate numbers, this is a jump of 4.3% for classic theme sites and 8% for block theme sites, which is nothing short of amazing. See the [source for LCP passing rate changes for sites that no longer lazy-load LCP image and use fetchpriority correctly](https://colab.research.google.com/drive/1lbTFTy1IoifpqkynKuualVjrLVSj1i0r#scrollTo=npwhv_NC20mu). * Of course this only applies to a subset of sites, however the accuracy of the lazy-loading heuristics has notably improved as well: 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)**, so this multiplies the above LCP improvements horizontally. See the [source for the accuracy comparison of how many sites (correctly) no longer lazy-load their LCP image](https://colab.research.google.com/drive/1lbTFTy1IoifpqkynKuualVjrLVSj1i0r#scrollTo=JO9k-_tPiNjX). ## Explaining the metrics ### Tooling used [HTTP Archive](https://httparchive.org/) is an open-source project that runs a pipeline across millions of URLs every month to monitor the state of the web, recording aspects like which technologies are used, how specific web features are being leveraged, how many HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tags or attributes of a specific kind are present on pages, and much more. The [Core Performance Team](https://make.wordpress.org/performance/) has been heavily relying on this tool to measure success of specific features or enhancements in WordPress core releases. In fact, [HTTP Archive even monitors a few specific metrics that are specific to WordPress](https://github.com/HTTPArchive/custom-metrics/blob/main/dist/cms.js). The [Chrome User Experience Report](https://developer.chrome.com/docs/crux/) (short“ CrUX”) exposes [Core Web Vitals (CWV)](https://web.dev/vitals/#core-web-vitals) performance data for millions of URLs, based on how real-world Chrome users experience visiting those URLs. While the tool can be used for individual sites to monitor their Web Vitals (e.g. via [PageSpeed Insights](https://pagespeed.web.dev/)), the data can also be aggregated at a larger lens. While CrUX does not contain much data other than the actual Web Vitals metrics, intersecting its dataset with that of HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. Archive allows gathering valuable insights. For example, it becomes possible to group sites into specific segments (such as all sites that use WordPress) and measure their CWV passing rates. Both HTTP Archive and CrUX expose data aggregated on a monthly basis. Joining data from HTTP Archive with data from CrUX is the foundation for tools like the [Core Web Vitals Technology Report](https://cwvtech.report), which displays CWV passing rates for numerous technologies over time. The dashboard also includes WordPress-specific passing rates, which can be helpful to look at for a quick overview of how WordPress sites are performing on the web at a glance. However, it should be noted that those numbers are quite broad, since the passing rates are based on _all_ WordPress sites in the dataset, regardless of the version used or any other factors. Therefore, in order to assess the impact of a specific WordPress release such as 6.3, a more granular approach is needed. ### Methodology The [WordPress 6.3 performance summary post](https://make.wordpress.org/core/2023/08/07/wordpress-6-3-performance-improvements/) highlighted two client-side performance enhancements as the main sources for the improved LCP performance, which are the optimizations of the emoji loader script( see [#58472](https://core.trac.wordpress.org/ticket/58472)) and the lazy-loading fixes plus the newly added support for the `fetchpriority` attribute, which are closely related (see the [WordPress 6.3 image performance enhancements post](https://make.wordpress.org/core/2023/07/13/image-performance-enhancements-in-wordpress-6-3/)). To assess whether those enhancements resulted in the anticipated LCP improvement, two analyses were conducted specific to those efforts. Additionally, a broader analysis was conducted to compare the LCP performance of WordPress 6.3 and WordPress 6.2 sites overall, as well as their [Time to First Byte (TTFB)](https://web.dev/ttfb/) performance, which directly impacts LCP as well. While with broader analyses like this one it is impossible to directly connect it to specific enhancements or fixes that launched as part of that release, it is crucial to look at the performance impact as a whole as well to get an idea how successful the release is at scale, regardless of how a specific feature is being used. The analyses were conducted by running various BigQuery queries against the intersection of HTTP Archive and CrUX datasets, specifically zooming in on only the sites that were using WordPress 6.2 in July 2023 and WordPress 6.3 in August 2023. To present the approach, queries, and results transparently, the research tool [Colab](https://colab.research.google.com/) was used. The links below point to the three Colabs with the analyses. They are quite detailed, so for a quick summary you may want to continue reading this post first. Please feel free to dive into the individual Colabs and their details, which you can also use to validate the summary below. Potentially you will find other notable metrics to highlight, or additional conclusions to draw. * [Lazy-loading & fetchpriority accuracy and LCP impact analysis](https://colab.research.google.com/drive/1lbTFTy1IoifpqkynKuualVjrLVSj1i0r) * [Emoji loader script optimization LCP and INP impact analysis](https://colab.research.google.com/drive/1KY0rbwYsubZSa3uI9Lu-P2n2UlJo_y0C) * [Comparing LCP and TTFB between WordPress 6.3 and 6.2](https://colab.research.google.com/drive/1-mrV_JOt93BqL8WahdBwhexbAExXGHMd) It should be noted that any field metrics need to be interpreted carefully as they always contain some degree of noise. Websites change over time in many ways, and it is impossible to eliminate external factors from the data. For example, a WordPress site may be slower with WordPress 6.3 than it was in 6.2 simply because it activated a new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. in the meantime that impacts performance. Such scenarios cannot be reliably detected and are therefore part of the metrics as well. Fortunately, the number of WordPress sites in the dataset is quite large: Looking at only the WordPress sites in the dataset that match the aforementioned criteria, we are looking at more than 500,000 WordPress home page URLs. This means that such specific side effects of individual sites usually have only negligible impact when looking at the overall data. Still, this is something to keep in mind: While field data is the closest there is available to assess the actual performance impact of a change, field data cannot be used to confidently claim that something is true or false — it has to be interpreted. ## Conclusion The large positive LCP impact confirms that the 6.3 release is an important milestone for WordPress performance. The numbers are particularly impressive on the sites for which the lazy-loading behavior was fixed and where `fetchpriority` support was correctly added. This shows the potential vertical impact that a few specific changes like that can have. Of course the overall LCP improvements are not _as_ high, but it confirms this is a large opportunity: By further improving the heuristics so that they apply correctly to more WordPress sites, the horizontal impact of the change can be increased so that in the future the large LCP benefits may scale to even more sites. Another metaMeta Meta 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. observation worth noting is that the LCP passing rate improvements in WordPress 6.3 compared to 6.2 for the correct behavior above (16-21% higher LCP passing rate) is actually not too far off from the lab benchmarks measured for 6.3 a few months ago (18-27% faster LCP). This makes sense, given that for lab benchmarks the test site was a simulated scenario where lazy-loading and `fetchpriority` were behaving correctly. It is great to know that the lab benchmarks carry some weight even when compared to the field impact. Last but not least, there are also two points to be highlighted which show that there is still room for improvement: * The accuracy with which `fetchpriority="high"` is applied to the LCP image is only around 50% across all scenarios. While this is okay for the newly added support of the attribute, it is clearly something to follow up on. Getting the heuristics for applying `fetchpriority` right is even more challenging than not lazy-loading the LCP image especially since the LCP image may differ between different viewports, but it’s safe to say there should be more that WordPress core can do in that area. At least, it is relieving to see that the negative LCP impact of adding `fetchpriority="high"` to the wrong image is fairly low, compared to the negative LCP impact of lazy-loading the LCP image. See the [source for fetchpriority accuracy against the LCP image](https://colab.research.google.com/drive/1lbTFTy1IoifpqkynKuualVjrLVSj1i0r#scrollTo=anEmaDrbqPsE) and the [source for LCP passing rate changes for sites that no longer lazy-load LCP image but use fetchpriority incorrectly](https://colab.research.google.com/drive/1lbTFTy1IoifpqkynKuualVjrLVSj1i0r#scrollTo=ST1b1GW_31di). * At a higher level, the Time to First Byte (TTFB) passing rate is not seeing much of an improvement and in parts is even regressing: For mobile viewports, the TTFB passing rate is improving between 1.6-1.7%, while for desktop viewports it is regressing by ~4.9% for classic theme sites and ~9% for block theme sites. It’s impossible to connect that to specific changes that landed in WordPress 6.3, and as mentioned before it could be affected by external factors, but it clarifies that server-side performance needs to continue to be a point of focus. See the [source for overall TTFB passing rate changes](https://colab.research.google.com/drive/1-mrV_JOt93BqL8WahdBwhexbAExXGHMd#scrollTo=2a4t0e7GnN4g). Please feel free to take a closer look at the analyses and leave your feedback as comments on this post. Additional thoughts, observations and questions are much appreciated. _Props [@joemcgill](https://profiles.wordpress.org/joemcgill/) [@westonruter](https://profiles.wordpress.org/westonruter/) for proofreading._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#analysis](https://make.wordpress.org/core/tag/analysis/), [#performance](https://make.wordpress.org/core/tag/performance/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:33 pm _on_ August 23, 2023 Tags: 6-3, 6.3.1, [minor releases ( 38 )](https://make.wordpress.org/core/tag/minor-releases/), [releases ( 56 )](https://make.wordpress.org/core/tag/releases/)    # 󠀁[WordPress 6.3.1 RC1 is now available](https://make.wordpress.org/core/2023/08/23/wordpress-6-3-1-rc1-is-now-available/)󠁿 WordPress 6.3.1 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release: * Use the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/) pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. - As this is a minor RCrelease candidate One 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)](https://make.wordpress.org/core/tag/6-3/?output_format=md#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](https://make.wordpress.org/core/handbook/contribute/codebase/). * Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) to test: `wp core update `[https://wordpress.org/wordpress-6.3.1-RC1.zip](https://wordpress.org/wordpress-6.3.1-RC1.zip) * [Directly download the Beta/RC version](https://wordpress.org/wordpress-6.3.1-RC1.zip). ## What’s in this release candidate? 6.3.1 RC1 features [4 fixes on Core](https://core.trac.wordpress.org/query?status=closed&milestone=6.3.1&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&col=keywords&order=priority) as well as [6 fixes](https://github.com/orgs/WordPress/projects/103/) for the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor. The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed: * [Fatal error on single-site get_users() under certain circumstances](https://core.trac.wordpress.org/ticket/59011) * [Editor: Incorrect error handling when converting classic to block menus](https://core.trac.wordpress.org/ticket/58823) * [Revert the last instance of str_starts_with() in update-core.php](https://core.trac.wordpress.org/ticket/59145) * [Update npm packages with critical bugfixes for 6.3.1](https://core.trac.wordpress.org/ticket/59151) The following block editor issues from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) are fixed: * [Multiple block select cut and paste failing](https://github.com/WordPress/gutenberg/issues/53774) * [Fix crash by moving editor style logic into a hook with useMemo](https://github.com/WordPress/gutenberg/pull/53596) * [Footnotes: Fix recursion into updating attributes when attributes is not an object](https://github.com/WordPress/gutenberg/pull/53257) * [Footnotes: autosave is not slashing JSON](https://github.com/WordPress/gutenberg/pull/53664) * [Footnotes: fix accidental override](https://github.com/WordPress/gutenberg/pull/53663) * [Footnotes: checking type before using count()](https://github.com/WordPress/gutenberg/pull/53660) ## What’s next? The developer-reviewed workflow ([double committer sign-off](https://make.wordpress.org/core/handbook/about/release-cycle/releasing-beta-versions/#double-committer-signoff)) is now in effect when making changes to the 6.3 branchbranch A 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, August 29th, 2023. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel. A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test! The WordPress 6.3.1 release is led by [@audrasjb](https://profiles.wordpress.org/audrasjb/) and [@azaozz](https://profiles.wordpress.org/azaozz/) with the help of [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) at mission control. [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-3-1](https://make.wordpress.org/core/tag/6-3-1/), [#minor-releases](https://make.wordpress.org/core/tag/minor-releases/), [#releases](https://make.wordpress.org/core/tag/releases/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 6:30 pm _on_ August 23, 2023 Tags: 6-3, [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [core ( 721 )](https://make.wordpress.org/core/tag/core/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/) # 󠀁[A Week in Core – August 21, 2023](https://make.wordpress.org/core/2023/08/23/a-week-in-core-august-21-2023/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between August 14 and August 21, 2023. * 27 commits * 34 contributors * 64 tickets created * 6 tickets reopened * 50 tickets closed Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=08%2F21%2F2023&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component and/or focus. ## Code changes ### Administration * Add function to standardize adminadmin (and super admin) notices – [#57791](https://core.trac.wordpress.org/ticket/57791) * Apply admin notice functions in multisitemultisite Used 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** – [#57791](https://core.trac.wordpress.org/ticket/57791) * Invalidinvalid A 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. argument passed in additional_classes– [#57791](https://core.trac.wordpress.org/ticket/57791) ### Build/Test Tools * Don’t send a SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) notice when a workflow fails once – [#58867](https://core.trac.wordpress.org/ticket/58867) * Measure additional load time metrics in performance tests – [#58360](https://core.trac.wordpress.org/ticket/58360) * Revert Slack messaging changes – [#58867](https://core.trac.wordpress.org/ticket/58867) * Send a failure notice in Slack when a run fails to start – [#58867](https://core.trac.wordpress.org/ticket/58867) * Simplify the required prerequisite jobs for the `failed-workflow` job – [#58867](https://core.trac.wordpress.org/ticket/58867) * Update PHPUnit Polyfills to version 1.1.0 – [#59150](https://core.trac.wordpress.org/ticket/59150) * Use the correct variable for checking the previous conclusion – [#58867](https://core.trac.wordpress.org/ticket/58867) ### Coding Standards * Improve variable names in `wp_save_image()` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-admin/includes/image-edit.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-admin/includes/meta-boxes.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) ### Docs * Add missing `@` to the return tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) in the` wp_get_theme_data_template_parts` function – [#59003](https://core.trac.wordpress.org/ticket/59003) * Correct punctuation in some instances of the `$crop` parameter description – [#58833](https://core.trac.wordpress.org/ticket/58833) * Fix typo in duplicate hook references for `views_{$this->screen->id}` – [#59102](https://core.trac.wordpress.org/ticket/59102), [#58833](https://core.trac.wordpress.org/ticket/58833) * Miscellaneous docblockdocblock (phpdoc, xref, inline docs) corrections and improvements– [#58833](https://core.trac.wordpress.org/ticket/58833) ### Editor * Ensure defer loading strategy is only applied to a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.’s viewScript – [#59115](https://core.trac.wordpress.org/ticket/59115) * Fix error handling of converting classic to block menus – [#58823](https://core.trac.wordpress.org/ticket/58823) * Use defer loading strategy for block view scripts – [#59115](https://core.trac.wordpress.org/ticket/59115) * update npm packages with critical bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions( adverse changes from the previous version) being the highest priority. fixes for 6.3.1 – [#59151](https://core.trac.wordpress.org/ticket/59151) ### General * Revert the last use of `str_starts_with()` in `update-core.php` – [#59145](https://core.trac.wordpress.org/ticket/59145) ### Media * Standardise documentation of the `$crop` parameter for various media functions and methods – [#58833](https://core.trac.wordpress.org/ticket/58833) ### Posts, Post Types * Remove redundant function calls in `get_body_class()` – [#43661](https://core.trac.wordpress.org/ticket/43661) ### REST APIREST API The 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/](https://developer.wordpress.org/rest-api/)󠁿 * Correct the docblocks for various permission related methods – [#58833](https://core.trac.wordpress.org/ticket/58833) ### Site Health * Correct the check for disk space available to safely perform updates – [#59116](https://core.trac.wordpress.org/ticket/59116) ### Themes * Add `wp_get_theme_data_custom_templates` function – [#59137](https://core.trac.wordpress.org/ticket/59137) ## Props **Thanks to the 50 people who contributed to WordPress Core on Trac last week:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) (3), [@costdev](https://profiles.wordpress.org/costdev/)( 2), [@aristath](https://profiles.wordpress.org/aristath/) (2), [@joedolson](https://profiles.wordpress.org/joedolson/)( 2), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (2), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 2), [@afercia](https://profiles.wordpress.org/afercia/) (2), [@poena](https://profiles.wordpress.org/poena/)( 2), [@joemcgill](https://profiles.wordpress.org/joemcgill/) (2), [@mukesh27](https://profiles.wordpress.org/mukesh27/)( 2), [@westonruter](https://profiles.wordpress.org/westonruter/) (2), [@flixos90](https://profiles.wordpress.org/flixos90/)( 1), [@gziolo](https://profiles.wordpress.org/gziolo/) (1), [@oandregal](https://profiles.wordpress.org/oandregal/)( 1), [@rajinsharwar](https://profiles.wordpress.org/rajinsharwar/) (1), [@youknowriad](https://profiles.wordpress.org/youknowriad/)( 1), [@swissspidy](https://profiles.wordpress.org/swissspidy/) (1), [@nithins53](https://profiles.wordpress.org/nithins53/)( 1), [@Presskopp](https://profiles.wordpress.org/presskopp/) (1), [@mathsgrinds](https://profiles.wordpress.org/mathsgrinds/)( 1), [@mattkeys](https://profiles.wordpress.org/mattkeys/) (1), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/)( 1), [@dasnitesh780](https://profiles.wordpress.org/dasnitesh780/) (1), [@sakibmd](https://profiles.wordpress.org/sakibmd/)( 1), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) (1), [@ramonopoly](https://profiles.wordpress.org/ramonopoly/)( 1), [@ayeshrajans](https://profiles.wordpress.org/ayeshrajans/) (1), [@jrf](https://profiles.wordpress.org/jrf/)( 1), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (1), [@antonvlasenko](https://profiles.wordpress.org/antonvlasenko/)( 1), [@get_dave](https://profiles.wordpress.org/get_dave/) (1), [@dlh](https://profiles.wordpress.org/dlh/)( 1), [@oglekler](https://profiles.wordpress.org/oglekler/) (1), and [@NekoJonez](https://profiles.wordpress.org/nekojonez/)( 1). **Congrats and welcome to our new contributor of the week:** [@mathsgrinds](https://profiles.wordpress.org/mathsgrinds/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 8), [@desrosj](https://profiles.wordpress.org/desrosj/) (5), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 3), [@joedolson](https://profiles.wordpress.org/joedolson/) (3), [@oandregal](https://profiles.wordpress.org/oandregal/)( 2), [@westonruter](https://profiles.wordpress.org/westonruter/) (2), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)( 1), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) (1), [@azaozz](https://profiles.wordpress.org/azaozz/)( 1), and [@swissspidy](https://profiles.wordpress.org/swissspidy/) (1). [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/get_dave/) [David Smith](https://profiles.wordpress.org/get_dave/) 2:21 pm _on_ August 23, 2023 Tags: 6-3, [dev-notes ( 616 )](https://make.wordpress.org/core/tag/dev-notes/), [dev-notes-6.3 ( 17 )](https://make.wordpress.org/core/tag/dev-notes6-3/), [navigation ( 4 )](https://make.wordpress.org/core/tag/navigation/), [navigation-block ( 3 )](https://make.wordpress.org/core/tag/navigation-block/) # 󠀁[What’s new for Navigation in WordPress 6.2 and 6.3](https://make.wordpress.org/core/2023/08/23/whats-new-for-navigation-in-wordpress-6-2-and-6-3/)󠁿 _This post was co-authored by [@scruffian](https://profiles.wordpress.org/scruffian/)._ Since the [last update](https://make.wordpress.org/core/2022/01/07/the-new-navigation-block/), contributors have added many new features to the Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. and _also_ the wider navigation management system within WordPress. These improvements are designed to help users manage their navigation menus and provide a more consistent and reliable experience. Let’s take a look at what’s changed… # Navigation List View One aspect of the navigation block is that parts of it are often hidden – for example submenus aren’t always open. This can make managing the items within a navigation block in the editor canvas challenging.  For this reason, [WordPress 6**.**2** **added an editable “List View” component to the navigation block inspector](https://github.com/WordPress/gutenberg/issues/42257) controls which lays out the navigation structure with every item visible: ![](https://lh4.googleusercontent.com/NiDdfJVXtK1blYln53dVpXHm8BL96rla1GFaJsbM3lM_Ox6RWpC1bvT75p- SDAWlQQmEW7xJRX63_Xt33_FnH21D-wMsIyAhmdQzVvcGRwlRzK-gDdDbFLJhd1SylDmoXcdLnal_kx69L9V- fQxu_xM) In addition to the standard block tools, the list view allows all the usual ways of managing navigation items. You can: * Add and remove navigation items. * Reorder navigation items. * Create new submenus. Adding this feature to the block also prepared the groundwork to allow contributors to unlock several exciting new features in WordPress 6.3. # Navigation in Site View With WordPress 6.3, it is now possible to manage your navigation from _outside_ of the context of a Navigation block and without needing to edit a template.  When in the Site Editor a new “Navigation” section is available within the Site View sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. which [lists all of your navigation menus](https://github.com/WordPress/gutenberg/issues/50578) and [allows you to manage them](https://github.com/WordPress/gutenberg/issues/50579) without having to find the templates (and blocks) they are used within: ![](https://lh3.googleusercontent.com/8Y6rdJ0N2Pm5qJPbOY-uj7QLMyKvr2T9EJzrZ1dSTRJ7vWtrL40Rw1RDOsQV0htBB4U- FnZs5cG52fUKV8zJTV9QjgPTk9IQyghoRvljjGIa6LZZENXKE5HwxkwEMqt4qmcN0GesX796YfhB34r6v0c) ![](https://lh6.googleusercontent.com/iU5BnGVyIrDtJYOZN7HkFICdP0Uzwcr-eiTw90SwhgSwpUxC3mFUc8NfNjUCCIGJRkjV8HDi8fm3r3GIlpum3mptwnnUUphjAnYWxA6u9ILzAxxvVj0k2sS2_adDY6YPHhcuXxl8FvPmq8stOY7Y488) One you click through to a Navigation you can: * Rename, duplicate and delete navigation. * Reorder items within a navigation. **Known limitation**: currently you cannot add new items, but [contributors are considering avenues to enable this for a future release](https://github.com/WordPress/gutenberg/issues/50580). One benefit of this view is that when multiple blocks all share the _same_ navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site., the user now has a single place to manage the menu items. # Focus Mode for Navigation Surfacing navigation as a list within the Site View is excellent for simple use cases, but sometimes it’s useful to see the navigation within the editor canvas to better visualize the changes being made. For this reason WordPress 6.3 sees the addition of [“Focus Mode” for Navigation](https://github.com/WordPress/gutenberg/issues/37950) whereby the navigation menu is displayed within an editor canvas completely isolated from any surrounding site context. You can access this new mode by clicking on the “Edit” button within the Navigation block’s toolbar, or by browsing to an individual navigation from the “Navigation” section of the Site View sidebar. ![](https://lh4.googleusercontent.com/sFjzoSUx8xFzdYSa-SMa77UNdF-BKh-0HsTdBNeeapkcGq6evKQmONmFCtL_Om- hWcQNC1kZJ2F7s3C1a5sXh85MALW7XUFyXKUqDJWsi_PevvX0MQgXlc7oLee8JWWYLkoK8nNpBIFc0uxaZ7jrxrs) Focus mode provides full scope to modify the blocks that are _inside_ the navigation block (the “menu items”), allowing you to add new items and even make use of the editable list view in the block’s  sidebar: ![](https://lh6.googleusercontent.com/hX417TN8JpCvSJWhgMvsKVdvMbF0tOxO8IBCsHkKx1OiI5XvIf4wvLOIcKLzEqcNHxpPHAw1h3leFOMsjVjjKihq- 14DeaL_7kmMwDoEQTcP3e_K8ObbuOXa33aKCvMENR1jvTXzdQ_pJW26nKRPfEM) It is important to note that as a given navigation menu may be used across _multiple_ block’s on a site – each of which will have their own place within the overall design of your site – the ability to change the visual representation of the Navigation block _itself_ has been intentionally disabled.  This allows you to focus soley on the contents of the navigation menu. Another benefit of this feature is that it is now possible to access and edit the inner blocks of a navigation simply by switching the editor to “code view” mode: ![](https://lh3.googleusercontent.com/9Tggdvty9W5mvzTdGDr7j8gtz5uK7NgO_HgIWjahYTAjImmc0owTGoYwlug_lhjdgLm1b4o3_5aINZOYVtDxzzOnG545POvIKPWCiqEaNvufURWMKkOzQWeu3- YB-dUmgZ6QneubMOwZfFHiEdKm-mA) Managing your navigation in isolation can be extremely useful, but sometimes it’s handy to see your navigation menu within the context of which it is being displayed. This is precisely what the next feature seeks to address. # Navigation in Patterns and Template Parts Patterns and Template Parts often contain navigation block’s. The classic example of this is a “HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.” template part containing a site logo block and a navigation block. In WordPress 6.3, when editing a template part or a pattern that contains a navigation _block_, you will see any associated [navigation _menu_ displayed in the sidebar in an editable list view](https://github.com/WordPress/gutenberg/issues/50704). ![](https://lh4.googleusercontent.com/rXsI_n2hfVfFkeICeHXNAbbQt8pnMV0tUizAd4a3RMgxiT7_5sIe6Nz1ZWSYa8xOLf210iVvomePmiTVPsC3Tz1- W52E9AIJlbYF8ag_Lzuo1BbFFqsaUjy7Os5Ly_ppKki6jiRpSzGmiktaO536vBU) This gives you quick access to manage the navigation that is used in the canvas without needing to switch to editing the block directly within the canvas itself. Moreover, by displaying the _name_ of the navigation in the sidebar, it is immediately apparent which navigation menu is being used by the block. In the future it may be possible to complement this in a reciprocal way when [viewing a single Navigation Menu by listing the templates where the navigation is used](https://github.com/WordPress/gutenberg/issues/53170). # Automatic creation of Navigation fallbacks Previous versions of WordPress had the concept of a “fallback” Navigation which was utilized in scenarios where a Navigation block has no navigation menu associated with it.  Depending on whether the site had existing Navigation Menus, the mechanism would either fetch an _existing_ navigation or _create a new_ _one_ from scratch. However the implementation provided a suboptimal user experience, with a noticeable loading delay upon block _modification_ caused by fetching/creating the (“fallback”) navigation menu to be associated with the block. With WordPress 6.3 however, this experience has been greatly improved with [each Navigation block now being _automatically_ assigned a navigation menu upon _insertion_](https://github.com/WordPress/gutenberg/pull/48698). This means that once a block is ready, edits will not trigger further “loading” delays as changes are simply synchronized to the navigation menu already associated with the block. ### Technical Implementation This has been achieved by moving the majority of the fallback logic to the WordPress REST APIREST API The 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/](https://developer.wordpress.org/rest-api/). A new dedicated “Navigation Fallback” endpoint now immediately returns the most “ suitable” fallback navigation menu for your site. What does “suitable” mean? This is much the same as for WordPress 6.2, namely when called the endpoint… * Returns the _most recently created_ existing Navigation Menu. * (if not available then…) Returns a Navigation Menu created from the _most recently created Classic Men_u (note: this is a one time import, and changes to the original Classic Menu are not synced to the block-based Navigation Menu). * (if not available then…) _Creates and returns a new Navigation Menu_, typically comprising a list of the current site’s Pages. This heuristic may evolve in _future_ releases to allow the fallback to be sensitive to the context in which it is being displayed. For now however, the improvement to the block’s user experience and reliability is a welcome improvement over previous versions. ### Opting out of automatic fallback creation If you’d like to opt out of automatic creation of Navigation fallbacks you can use the `wp_navigation_should_create_fallback` hook as follows: ```wp-block-code add_filter( 'wp_navigation_should_create_fallback', '__return_false' ); ``` See the [original PR for full details](https://github.com/WordPress/wordpress-develop/pull/4813). # Other improvements ## Performance On top of the improvements to perceived performance delivered by improving the fallback navigation system, WordPress 6.3 also provides an additional enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to the performance of the navigation system. In [#48683](https://github.com/WordPress/gutenberg/pull/48683) contributors [added the navigation endpoints to the list of endpoints that are _preloaded_ in the editor](https://github.com/WordPress/gutenberg/pull/48683). This means that when the editor loads the list of navigation menus will _already be available_ to display and use within the block and/or Site View sidebar.  This simple change makes it possible to access and manage your navigation, which is a key facet of most websites and makes for a greatly improved user experience. ## Login/Logout It is common for websites to provide a login and logout link for their users. In [#49160](https://github.com/WordPress/gutenberg/pull/49160)  we added this block to the list of blocks that are allowed within the navigation block so that users can add this functionality to their navigation. # What do you think? This concludes our brief overview of the key changes to the navigation system in WordPress.  As always we are open to your feedback. What do you think? Are these improvements impactful for you? What is missing and what you would like to see? Your thoughts are appreciated in the comments below. **Bugs** – we appreciate it if any bugs are [reported on Github](https://github.com/WordPress/gutenberg/issues/new/choose). ## What’s next? Of course, whilst there has been much progress contributors recognise that there is still _much_ to do. Our focus for future releases will be  [updated on the relevant Tracking Issue](https://github.com/WordPress/gutenberg/issues/38275#issuecomment-1619747714) and we encourage you all to take a look and let us know any feedback you might have on the proposals outlined there. You can also join us on WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)( sign up required) in the [#feature-website-navigation channel](https://wordpress.slack.com/archives/C01KDAZJMQ9). Props to [@scruffian](https://profiles.wordpress.org/scruffian/) who co-authored this post and to @draganescu and [@annezazu](https://profiles.wordpress.org/annezazu/) for review. [#6-3](https://make.wordpress.org/core/tag/6-3/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/), [#dev-notes6-3](https://make.wordpress.org/core/tag/dev-notes6-3/), [#navigation](https://make.wordpress.org/core/tag/navigation/), [#navigation-block](https://make.wordpress.org/core/tag/navigation-block/) [ ](https://profiles.wordpress.org/ironprogrammer/) [Brian Alexander](https://profiles.wordpress.org/ironprogrammer/) 6:27 pm _on_ August 17, 2023 Tags: 6-3, [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [dev chat ( 899 )](https://make.wordpress.org/core/tag/dev-chat/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [summary ( 966 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev Chat Summary, August 16, 2023](https://make.wordpress.org/core/2023/08/17/dev-chat-summary-august-16-2023/)󠁿 The WordPress Developers Chat meeting took place on [August 2, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230802T2000) in the [core](https://wordpress.slack.com/messages/core/) channel of [Make WordPress Slack](https://make.wordpress.org/chat/). ## Key Links * [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1692216005854449) of the Dev Chat on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), hosted by [@ironprogrammer](https://profiles.wordpress.org/ironprogrammer/). * Today’s agenda: [Dev Chat agenda, August 16, 2023](https://make.wordpress.org/core/2023/08/15/dev-chat-agenda-august-16-2023/), courtesy [@webcommsat](https://profiles.wordpress.org/webcommsat/). ## Highlighted Posts * [Two Weeks in Core – August 14, 2023](https://make.wordpress.org/core/2023/08/16/a-week-in-core-august-14-2023/)— Thank you, [@audrasjb](https://profiles.wordpress.org/audrasjb/), for these updates! > Here’s an overview of what’s happened in TracTrac An open source project by Edgewall > Software that serves as a bug tracker and project management tool for WordPress. > between July 31 and August 14, 2023: > * 40 commits > * 50 contributors > * 164 tickets created > * 15 tickets reopened > * 138 tickets closed > * _and 5 new contributors in this period_ ❤️ * [Status update on the Interactivity API](https://make.wordpress.org/core/2023/08/15/status-update-on-the-interactivity-api/): Get the latest updates on this proposal and where to track its progress. This post also includes info on valuable learning resources so you can dive in and explore the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.’s possibilities. * [What’s new for developers? (August 2023)](https://developer.wordpress.org/news/2023/08/whats-new-for-developers-august-2023/): Do “new shiny objects”, “bag of goodies”, and “kid in a toy shop” spark your interest? Thought so! Check out the newest stuff in 6.3 and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) in this latest post on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)’ s own Developer Blogblog (versus network, site). * [What’s new in Gutenberg 16.4](https://make.wordpress.org/core/2023/08/10/whats-new-in-gutenberg-16-4-9-august/): _Inside:_ A new progress bar component, updates to the Command Palette and Footnotes blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., and auto-inserting blocks are highlighted in the latest pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. release. * ⏰ Reminder: Share your comments on the [ticket ownership discussion](https://make.wordpress.org/core/2023/08/01/whose-ticket-is-it-anyway/) by **September 1, 2023**. ## Release Updates ### WordPress 6.3 * See the [WordPress 6.3 developer notes](https://make.wordpress.org/core/tag/dev-notes+6-3/). The Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/). The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. has had 6,500 views since it was published on July 18! ### WordPress 6.3.1 * There are some [urgent fixes](https://github.com/WordPress/gutenberg/commits/wp/6.3) that have been identified for a quick turnaround 6.3.1 release, but as of this writing, timing is still being decided. For the latest updates, follow discussions in the [#6-3-release-leads](https://wordpress.slack.com/archives/C051Z1SKBDZ) channel. ### WordPress 6.4 Stay in the loopLoop The 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](https://codex.wordpress.org/The_Loop) with 6.4 by checking out: * [WordPress 6.4 Development Cycle](https://make.wordpress.org/core/6-4/) hub * [6.4 Editor tasks board](https://github.com/orgs/WordPress/projects/127) * and following along in the [#6-4-release-leads](https://wordpress.slack.com/archives/C055Y7FKS7N) channel ## Maintainers: Component Help Requests ### Rollback Auto Updates – Part 3 The [Rollback Update Failure](https://wordpress.org/plugins/rollback-update-failure/) plugin has received several recent updates, and is awaiting security audit and additional feedback. ### Plugin Dependencies [Plugin dependencies (Trac #22316)](https://core.trac.wordpress.org/ticket/22316) has been updated with the latest round of feedback, and is ready for commit consideration. [Trac #59112](https://core.trac.wordpress.org/ticket/59112) has been created to encompass remaining design input for this feature, which could be incorporated during the feature’s merge to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. ## Open Floor ### WCUS 2023 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of 󠀁[https://make.wordpress.org/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://2017.us.wordcamp.org/contributor-day/](https://2017.us.wordcamp.org/contributor-day/)󠁿 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿 #### Make/Core Post WordCampWordCamp WordCamps 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](https://central.wordcamp.org/about/). US [Contributor Day](https://us.wordcamp.org/2023/contributor-day/) is next week! There is a Core blog [draft](https://make.wordpress.org/core/?p=107443&preview=1&_ppp=53874734a0) underway that aims to promote and provide info to new contributors ahead of the event. The post is to be finalized after Dev Chat, and it is requested that Core community members provide feedback in the [#core channel](https://wordpress.slack.com/archives/C02RQBWTW). Core Team RepTeam Rep A 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. [@webcommsat](https://profiles.wordpress.org/webcommsat/) is collating details for the event. #### Volunteers Needed Volunteers are needed to help facilitate _**in person at tables** and **remotely on Slack**_ during Contributor[ Day](https://us.wordcamp.org/2023/contributor-day/). Contributors are asked to raise their hand in Slack, or add their name and level of participation in the post comments. A handful of chat attendees raised their hands to help attend to Core tables throughout the day, as well as help remote attendees in Slack, but there are still no clear Core table leads. #### Ticketticket Created for both bug reports and feature development on the bug tracker. Focus There was a question about whether “ancient” Trac tickets should be a point of focus during Contributor Day, and there was general agreement that `good-first-bug` tickets were likely better candidates to focus on, given the limited time and resources available at the event. New contributors to Core are encouraged to set up their local environments in advance of WCUS, and to join the next New Core Contributor meeting on **[2023-08-23 at 19:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230823T1900)** in the [#core](https://wordpress.slack.com/archives/C02RQBWTW) channel. ### Fields API A status update was provided for the [WordPress Fields API](https://github.com/sc0ttkclark/wordpress-fields-api), with a Make/Core post to come later this week. Those interested in this project are invited to help with [project research](https://github.com/sc0ttkclark/wordpress-fields-api/blob/develop/docs/research.md), stop on by and chat with [@sc0ttkclark](https://profiles.wordpress.org/sc0ttkclark/) at WCUS, and to join the conversation over in the [#core-fields channel](https://wordpress.slack.com/archives/C04MWK7PZ). ### 6.4 Scrub Schedule The bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub schedule is still being finalized, but the first session is to take place on [2023-08-17 at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230817T1700) in [#core](https://wordpress.slack.com/archives/C02RQBWTW). All are welcome to join the scrub! ## Next Meeting The next meeting will be on [August 23, 2023 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230823T2000). Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the [`#core` Slack channel](https://wordpress.slack.com/archives/C02RQBWTW). _Props [@afragen](https://profiles.wordpress.org/afragen/) for peer review of this post._ [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 10:22 am _on_ August 16, 2023 Tags: 6-3, [6-4 ( 78 )](https://make.wordpress.org/core/tag/6-4/), [core ( 721 )](https://make.wordpress.org/core/tag/core/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/) # 󠀁[Two Weeks in Core – August 14, 2023](https://make.wordpress.org/core/2023/08/16/a-week-in-core-august-14-2023/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 31 and August 14, 2023. * 40 commits * 50 contributors * 164 tickets created * 15 tickets reopened * 138 tickets closed Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=08%2F14%2F2023&daysback=14&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component and/or focus. ## Code changes ### Build/Test Tools * Bump the required versions of Node.js and npm – [#56658](https://core.trac.wordpress.org/ticket/56658) * Correct two `@covers` annotations to use the recommended pattern – [#59069](https://core.trac.wordpress.org/ticket/59069) * Update 3rd-party GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) Actions – [#58867](https://core.trac.wordpress.org/ticket/58867) * Update all build tool related dependencies – [#58863](https://core.trac.wordpress.org/ticket/58863) * Update the README file to reflect new Node.js/npm versions – [#59071](https://core.trac.wordpress.org/ticket/59071), [#56658](https://core.trac.wordpress.org/ticket/56658) * revert downgrade of uuid – [#58623](https://core.trac.wordpress.org/ticket/58623) * Fix leakage in WP_List_Table tests – [#58955](https://core.trac.wordpress.org/ticket/58955), [#58896](https://core.trac.wordpress.org/ticket/58896) ### Code Modernization * Deprecate dynamic properties in WP_List_Table magic methods – [#58896](https://core.trac.wordpress.org/ticket/58896), [#56034](https://core.trac.wordpress.org/ticket/56034) * Deprecate dynamic properties in WP_Text_Diff_Renderer_Table magic methods – [#58898](https://core.trac.wordpress.org/ticket/58898), [#56034](https://core.trac.wordpress.org/ticket/56034) * Deprecate dynamic properties in WP_User_Query magic methods – [#58897](https://core.trac.wordpress.org/ticket/58897), [#56034](https://core.trac.wordpress.org/ticket/56034) * Use “declare” in WP_List_Table magic methods deprecation message – [#58896](https://core.trac.wordpress.org/ticket/58896) ### Coding Standards * Bring more consistency to `Last-Modified` and `ETag` checks – [#58831](https://core.trac.wordpress.org/ticket/58831) * Rewrite loose comparison in `wp_list_categories()` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use `instanceof` keyword instead of the `is_a()` function – [#58943](https://core.trac.wordpress.org/ticket/58943) * Use strict comparison in `wp-admin/includes/class-wp-importer.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-includes/class-wp-image-editor.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-includes/class-wp.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-includes/cron.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-includes/kses.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) * Use strict comparison in `wp-includes/revision.php` – [#58831](https://core.trac.wordpress.org/ticket/58831) ### Docs * Correct duplicate hook reference for `wp_min_priority_img_pixels` – [#59067](https://core.trac.wordpress.org/ticket/59067) * Remove `@see` references for SimplePie classes – [#59030](https://core.trac.wordpress.org/ticket/59030) ### Editor * Only exclude auto-generated blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. files from coding standards checks – [#50010](https://core.trac.wordpress.org/ticket/50010) * Simplify usage of `block_has_support()` function by supporting a string – [#58532](https://core.trac.wordpress.org/ticket/58532) ### Embeds * Modernize wp-embed script with removal of obsolete IE10/IE11 code and support for WP 4.4 and below – [#58974](https://core.trac.wordpress.org/ticket/58974) ### Emoji * Suppress console errors from sessionStorage usage in sandboxed post embed iframeiframe iFrame 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. – [#58978](https://core.trac.wordpress.org/ticket/58978), [#58472](https://core.trac.wordpress.org/ticket/58472) ### External Libraries * Update Backbone.js to version `1.5.0` – [#58930](https://core.trac.wordpress.org/ticket/58930) * Update imagesLoaded to version `5.0.0` – [#56731](https://core.trac.wordpress.org/ticket/56731) * Update the `whatwg-fetch` polyfill library – [#59066](https://core.trac.wordpress.org/ticket/59066) ### HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. * Add support for BUTTON element – [#58961](https://core.trac.wordpress.org/ticket/58961) * Adjust code styling to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)’ s linter’s preferences – [#58918](https://core.trac.wordpress.org/ticket/58918) * Fix missing * for docblockdocblock (phpdoc, xref, inline docs) – [#58918](https://core.trac.wordpress.org/ticket/58918).– [#59010](https://core.trac.wordpress.org/ticket/59010) ### Media * Simplify logic in `wp_get_loading_optimization_attributes()` – [#58891](https://core.trac.wordpress.org/ticket/58891) ### Options, MetaMeta Meta 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. APIs * Expand `$autoload` parameter documentation – [#58963](https://core.trac.wordpress.org/ticket/58963) ### Script Loader * Use defer loading strategy for wp-embed script and move to head (in block themes)– [#58931](https://core.trac.wordpress.org/ticket/58931) ### Site Health * Use `PHP_SAPI` constant instead of the `php_sapi_name()` function – [#58942](https://core.trac.wordpress.org/ticket/58942) ### Themes * Avoid unnecessary check whether parent template file exists when not using a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. [https://developer.wordpress.org/themes/advanced-topics/child-themes/](https://developer.wordpress.org/themes/advanced-topics/child-themes/)– [#58576](https://core.trac.wordpress.org/ticket/58576) * add wp_get_theme_data_template_parts function – [#59003](https://core.trac.wordpress.org/ticket/59003) ### Upgrade/Install * Update `$_old_files` for 6.3 – [#58994](https://core.trac.wordpress.org/ticket/58994) ### Users * Correct the logic for `switch_to_blog()` in `WP_User_Query::generate_cache_key()`– [#59011](https://core.trac.wordpress.org/ticket/59011) ## Props **Thanks to the 50 people who contributed to WordPress Core on Trac last week:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) (13), [@aristath](https://profiles.wordpress.org/aristath/)( 7), [@rajinsharwar](https://profiles.wordpress.org/rajinsharwar/) (7), [@afercia](https://profiles.wordpress.org/afercia/)( 7), [@poena](https://profiles.wordpress.org/poena/) (7), [@costdev](https://profiles.wordpress.org/costdev/)( 6), [@jrf](https://profiles.wordpress.org/jrf/) (5), [@antonvlasenko](https://profiles.wordpress.org/antonvlasenko/)( 5), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (5), [@mukesh27](https://profiles.wordpress.org/mukesh27/)( 5), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (5), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)( 4), [@swissspidy](https://profiles.wordpress.org/swissspidy/) (4), [@desrosj](https://profiles.wordpress.org/desrosj/)( 4), [@hareesh-pillai](https://profiles.wordpress.org/hareesh-pillai/) (3), [@ayeshrajans](https://profiles.wordpress.org/ayeshrajans/)( 3), [@dmsnell](https://profiles.wordpress.org/dmsnell/) (3), [@flixos90](https://profiles.wordpress.org/flixos90/)( 3), [@westonruter](https://profiles.wordpress.org/westonruter/) (3), [@markjaquith](https://profiles.wordpress.org/markjaquith/)( 3), [@oglekler](https://profiles.wordpress.org/oglekler/) (3), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/)( 3), [@thekt12](https://profiles.wordpress.org/thekt12/) (2), [@nihar007](https://profiles.wordpress.org/nihar007/)( 2), [@nazsabuz](https://profiles.wordpress.org/nazsabuz/) (1), [@arnedb](https://profiles.wordpress.org/arnedb/)( 1), [@Hareesh](https://profiles.wordpress.org/hareesh/) (1), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/)( 1), [@Pillai](https://profiles.wordpress.org/pillai/) (1), [@JeffPaul](https://profiles.wordpress.org/jeffpaul/)( 1), [@joemcgill](https://profiles.wordpress.org/joemcgill/) (1), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/)( 1), [@crstauf](https://profiles.wordpress.org/crstauf/) (1), [@kevin940726](https://profiles.wordpress.org/kevin940726/)( 1), [@khokansardar](https://profiles.wordpress.org/khokansardar/) (1), [@Rahe](https://profiles.wordpress.org/rahe/)( 1), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) (1), [@valmedia2023](https://profiles.wordpress.org/valmedia2023/)( 1), [@dantovbein](https://profiles.wordpress.org/dantovbein/) (1), [@hbhalodia](https://profiles.wordpress.org/hbhalodia/)( 1), [@tmatsuur](https://profiles.wordpress.org/tmatsuur/) (1), @felixarntz (1), [@gziolo](https://profiles.wordpress.org/gziolo/) (1), [@ahmedgeek](https://profiles.wordpress.org/ahmedgeek/)( 1), [@dd32](https://profiles.wordpress.org/dd32/) (1), [@austinginder](https://profiles.wordpress.org/austinginder/)( 1), [@RavanH](https://profiles.wordpress.org/ravanh/) (1), [@lopo](https://profiles.wordpress.org/lopo/)( 1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), and [@rmccue](https://profiles.wordpress.org/rmccue/)( 1). **Congrats and welcome to our 5 new contributors of the week:** [@nazsabuz](https://profiles.wordpress.org/nazsabuz/), [@arnedb](https://profiles.wordpress.org/arnedb/), [@valmedia2023](https://profiles.wordpress.org/valmedia2023/), [@dantovbein](https://profiles.wordpress.org/dantovbein/), [@ahmedgeek](https://profiles.wordpress.org/ahmedgeek/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 14), [@desrosj](https://profiles.wordpress.org/desrosj/) (7), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)( 5), [@flixos90](https://profiles.wordpress.org/flixos90/) (4), [@westonruter](https://profiles.wordpress.org/westonruter/)( 3), [@bernhard-reiter](https://profiles.wordpress.org/bernhard-reiter/) (2), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 1), [@oandregal](https://profiles.wordpress.org/oandregal/) (1), [@jorbin](https://profiles.wordpress.org/jorbin/)( 1), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) (1), and [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)( 1). [#6-3](https://make.wordpress.org/core/tag/6-3/), [#6-4](https://make.wordpress.org/core/tag/6-4/), [#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) # Post navigation [← Older posts](https://make.wordpress.org/core/tag/6-3/page/2/?output_format=md)