6.3 Release Parties Schedule and hosts

This post aims to prepare a calendar with the expected start time for each release party and who is involved for the upcoming 6.3 milestones.
Things can change at the last minute, as we saw happening with 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, so expect some flexibility around it. The release team will do their best to respect the calendar and communicate any change promptly.
If you can fill any of those roles, please add your name in the comments, with the date and role, so I can finalize the calendar.

Itโ€™s ok also to have two people with the same access level for each party. This will allow us to help each other if the party takes longer than expected.

Thank you all for the team effort!

Monday, July 3, 2023, at 16:00 UTCMilestoneHostCommittercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.SecurityMission ControlMarcomms
Monday, July 3, 2023 at 16:00 UTCBeta 3@priethor@davidbaumwald@davidbaumwald@davidbaumwald@dansoschin (backup @meher)
Tuesday, July 11, 2023, at 16:00 UTCBeta 4@francina@sergeybiryukov, backup @davidbaumwald@sergeybiryukov, backup @davidbaumwald@davidbaumwald, backup @sergeybiryukov@meher (backup @dansoschin)
Tuesday, July 18, 2023, at 16:00 UTCRelease 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). 1@priethor@davidbaumwald@davidbaumwald@davidbaumwald@dansoschin (back up @meher)
Tuesday, July 25, 2023, at 16:00 UTCRelease Candidate 2@priethor@audrasjb@davidbaumwald@davidbaumwald and @audrasjb (mentee)@meher
Tuesday, August 1, 2023, at 16:00 UTCRelease Candidate 3@flixos90@sergeybiryukov, backup @davidbaumwald@sergeybiryukov, backup @davidbaumwald@sergeybiryukov, backup @davidbaumwald@meher (backup @dansoschin and @jpantani)
Monday, August 7, 2023, at 16:00 UTCDry Run@priethor (backup @francina)@davidbaumwald, backup
@sergeybiryukov
@davidbaumwald, backup
@sergeybiryukov
@davidbaumwald, backup @sergeybiryukov @dansoschin, @jpantani, @meher
Tuesday, August 8, 2023, at 17:00 UTC*General Release@francina and @priethor@davidbaumwald, backup
@sergeybiryukov
@davidbaumwald, backup
@sergeybiryukov
@davidbaumwald, backup @sergeybiryukov @dansoschin, @jpantani, @meher

General release is scheduled 1 hour later than the Dry Run to allow for 24 hours freeze.

#6-3, #release

Hallway Hangout: Performance Improvements for WordPress 6.3

Following up on prior performance related hallway hangouts, @clarkeemily and I will be cohosting an upcoming hallway hangout to discuss happenings for 6.3.

If youโ€™re interested in joining, the Hallway Hangout will happen onย 2023-07-27 15:00. a Zoom link will be shared in the #core-performance SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ย channel before starting.

At a high level, weโ€™ll go through quick intros (what each person does/focuses on) before diving into WordPress 6.3 performance improvements led by performance leads (@clarkeemily @flixos90) and looking ahead at what can be learned for WordPress 6.4. Hereโ€™s a preview from the 6.3 beta 2 post:

Following the incredibleย performance improvements introduced in 6.2, the release includes more than 170 performance-related updates, including addingย defer and async support to the WP Scripts APIย andย fetchpriority support for images. Optimizations were made toย block template resolution,ย image lazy-loading, and theย emoji loader, all of which benefit LCP performance. Support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher versionsย 8.0,ย 8.1, andย 8.2ย has been improved.ย 

As a reminder, hallway hangouts are meant to be casual and collaborative so come prepared with a kind, curious mind along with any questions or items you want to discuss around this important area of the project, especially since the agenda is intentionally loose to allow for it.

Noting this specifically for folks who have expressed interest previously or who are involved directly in this work cc @hellofromtonya @aristath @oandregal @tweetythierry @desrosj @youknowriad @spacedmonkey @adamsilverstein @mukesh27 @joemcgill @johnbillion.

Recording

Attendees

@adamsilverstein @mukesh27 @joemcgil @oandregal @clarkeemily @flixos90 @swissspidy @annezazu @poena @elmastudio @dlh @thekt12 @10upsimon @westonruter

Notes

After a round of intros for anyone who wanted to participate, we jumped into the following discussions.

Overview of 6.3 performance improvements

@flixos90 discussed an in-progress post rounding up performance improvements for 6.3, highlighting that thus far performance improvements are looking even better than for 6.2. Here are some quick stats from 6.3 RC2 shared yesterday:

LCP 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 ~28% faster than 6.2.2

  • TTFB ~22% faster
  • LCP-TTFB ~37% faster

LCP for classic themes ~19% faster than 6.2.2

  • TTFB ~1% slower
  • LCP-TTFB ~30% faster

We also went through the following 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.:

As part of the above item, itโ€™s important to note that dependencies for larger plugins are handled with care, opting for the more conservative pathway if broader extensions of a larger pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. havenโ€™t opted this approach when the overall plugin has. If both switch, this new approach will be used. While not a performance enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. out of the box using WordPress since it requires adoption, it is an important item to cover to ensure folks see how they can put it to use. As part of this, we discussed both Delay loading comment-reply script with async loading strategy and Use defer loading strategy for frontend view scripts with the latter already merged to improve loading performance for frontend scripts in WordPress itself. More here:ย 

Now that we have Script Loading Strategies committed, Iโ€™ve started exploring how we can take advantage of them to improve frontend performance in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./themes/plugins. As a first step, I wanted to try one set of enhancements to see what is involved and what the impact is to see whether the effort is worth it. As an initial exploration, I focused on the scripts that 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/ adds to the frontend, that is the block view scripts. These are unfortunately all added to theย headย and are all blocking. So opened a PR to leverage async and defer, and my findings a 19.3% reduction in LCP-TTFB!ย https://github.com/WordPress/gutenberg/pull/52536#:~:text=Performance%20Analysis

Weston in the #core-performance channel.

Diving into the data

Sparked by a question from @oandregal about when should we expect the improvements landed in 6.2 and 6.3 to impact RUM public datasets, we dug into data to see the impact of changes. Andrรฉ later shared a personal post on the topic! For context, lab data is what improvements we expect to see in a more contained environment where as field data is what we end up seeing on real sites. A note from Felix that we always have to wait at least a month after a new release to get a first set of metrics from the Chromeย UXย Report &ย HTTPย Archive. To help aid digging into data, block theme detection was added to the HTTP archive a few months ago.

As discussed, the key is to pull tendencies as itโ€™s hard to get absolutely exact data. Right now, the tendencies validates lab assumptions when looking into the field data! We went through reports both in Chrome UX Report data and Core Web vitals for TTFB:

Of note, data in CrUX is added at aggregate level and itโ€™s not weighted by number of pages so a site with tons of pages is equally weighted for one with none. For Core Web Vitals, it shows a steady increase since April and it shows that we can look for delayed impacts for 6.3 in September/October to see how changes are landing.

Discussion around PHP backports to Core

We ended talking about backports to Core and the impact on performance as the the current performance process involves analyzing the previous state of WordPress versions to identify opportunities for improvement, implementing those improvements, and validating their effectiveness. The performance team wants to be more proactive and involved in looking ahead at work to come to ensure that WordPress remains performant, particularly with new features like duotone functionality being added late in the development cycle. We talked about the efforts from @hellofromtonya to ease the backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. process as well as the current time constraints to do so. We have a shorter release cycle for 6.4 so thereโ€™s a chance that we can experiment a bit more to see if we can do more frequent package updates.

We discussed the idea of a mid-point merge for PHP backports and a more formal workflow for both Core and Gutenberg teams. The proposal included a โ€œPHP backport partyโ€ chat, similar to the release party chats, during the release cycle to facilitate collaboration ideally from more folks. We ended chatting about whether the Core Editor had a dedicated group on performance, explaining that there isnโ€™t a dedicated group so much as a collection of performance-minded individuals within the Gutenberg development.

@hellofromtonya as someone who spends so much time living in this space, Iโ€™d love to know what you think here and how myself and @clarkeemily can facilitate as co-members of the 6.4 release squad.

#hallwayhangout, #performance

Whatโ€™s new in Gutenberg 16.1? (29 June)

Whatโ€™s new in Gutenberg 16.1

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/ 16.1 is now available to download.

16.1 is loaded with exciting features, 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, 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) improvements and enhancements. Patterns, whose changes are synched across your site? Check. Automated footnotes for text blocks? You got it!

This release consists of 247 pull requests, authored by 72 contributors, including three new contributors. Whatโ€™s more, many of 16.1โ€™s highlights will be included in the upcoming WordPress 6.3 release.

Table of contents

  1. Your templates and patterns, your library
  2. Create your site without distraction
  3. Text blocks: now with footnotes
  4. Achieve more with the Site editor sidebar
  5. Worthy mentions
  6. Changelog
  7. Contributors

Your templates and patterns, your library

You can now create and sync design patterns across your entire site, and access them in the Pattern Library. (PR #51078)

โ€œReusable blocksโ€ have been renamed to โ€œPatternsโ€, and come with the option to synchronize.ย 

Changes you make to a synchronized pattern will update all instances of that pattern no matter where it appears on your site.ย ย 

Unsynchronized patterns, on the other hand, can be edited independently after being inserted.ย 

All your existing Reusable blocks, custom template parts, and patterns are displayed and are searchable in the Pattern Library. Theyโ€™re also available in 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. inserter.

Gutenberg Pattern Library

Create your site without distraction

Gutenberg 16.1 introducees a Distraction Free mode to the site editor; the same feature available for writing posts users love since Gutenberg 14.4 can now help you build your site, too. (PR #51173)

Once activated, this new mode removes all controls and menus, offering an environment for focused work while allowing you to edit a 1:1 preview of your site.

The Distraction Free setting is accessible via a keyboard shortcut Shift+Cmd+\ in Mac (Shift+Ctrl+\ in Windows) or in the top right options menu. โ€œCalm, blue oceanโ€ productivity is just a click away.

Text blocks: now with footnotes

Gone are the days of creating and constantly re-sorting dozens of anchor links. After a great deal of exploration and testing, automated footnote functionality comes to the Block Editor. (PR #51201)

Footnotes are available in text blocks including paragraph, heading and lists, and can be added from the block context menu.

The Footnotes block will remove and reorder your footnotes as you edit your text, which means less time managing links and lists and more time for writing.

Achieve more with the Site editor 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.

When viewing Home page templates, youโ€™ll now see more template settings and configuration details in the sidebar. (PR #51223) Quickly access the home templateโ€™s 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., footer and other template areas and control blogblog (versus network, site) options such as posts per page and allowing comments.

Site editor sidebar showing home template settings

When browsing a template part that contains one or more navigation menus, for example the Header template part, you will see those menus displayed in the sidebar. From here you can conveniently view and edit all the menu items featured in that template part. (PR #51492)

Furthermore, in 16.1, live theme previewing in the Site editor (introduced in 15.8) has been moved from beyond the experimental curtain, and is available for installed blocks themes under Appearance > Themes. (PR #50983)

Worthy mentions

Take control over the dimensions of Image blocks with new aspect-ratio tools. (PR #51545)

The Link Control UIUI User interface has also seen a major revamp in this release, streamlining the editing process further. (PR #50890)

#51831 makes it easier to shuffle your Button blocks to and fro and up and down by providing direction-based arrows in the context toolbar.

Changelog

Features

  • Add focus mode for Navigation Menus. (39286)
  • Allow renaming, duplication and deleting of Navigation menus from Browse Mode Sidebar. (50880)

Block Library

  • Add Navigation Menus to Template Parts screen sidebar in Browse Mode. (51492)
  • Add Footnotes block to text blocks. (51201)

Patterns

  • Allow for filtering of block patterns by source. (51672)
  • Reusable blocks: Rename to โ€˜Patternsโ€™ and add option to also add a non-synced Pattern. (51144)
  • Site Editor: Add Library for Template Parts & Patterns Management. (51078)

Themes

  • Remove the experiment option for Block Theme Previews. (50983)

Site Editor

  • Add distraction free to site editor (51173)

Enhancements

Site Editor

  • Edit Site: Make adminadmin (and super admin) background consistent with layout. (51741)
  • Edit Site: Remove first loading spinner. (51736)
  • Edit Site: Use global background color while loading. (51709)
  • Improve guidance to editing template when focused on editing a page. (51366)
  • Only show view site link in view mode. (51279)
  • Page Details View: Show featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. only if there is one. (51649)
  • Page Details View: Show parent only if there is one. (51648)
  • Site editor sidebar: Home template details. (51223)
  • Navigation on Browse Mode: Move the action to the leaf menu. (50843)
  • Remove TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. as an option in the add template flow. (51586)
  • Remove shadows in Site Editor sidebar. (51546)
  • Show warning on critical block removal. (51145)
  • Site editor navigation: Use chevron left in RTL mode. (51588)
  • Add ability to set status, publish date and password in site editor. (51408)
  • Add table view to manage templates page. (50766)
  • Update Library panel footer. (51652)
  • Update page list footer. (51438)
  • List draft navigations in Browse mode Navigation section. (51422)
  • Show actions for empty menus in Navigation on Browse mode. (51420)
  • Unify welcome guides labels casing. (51700)
  • Site editor sidebar: Add footer to template part and ensure nested template areas display. (51669)
  • Update colors in โ€˜Site viewโ€™. (51856)
  • Site Editor: Make string to add Template parts and Patterns consistent and translatable 51743

Components

  • ItemGroup: Update button focus styles to be more consistent. (51576)
  • Toolbar: Use Ariakit instead of Reakit. (51623)
  • Update: Adjust modal radius to be between frame and buttons. (51254)
  • UnitControl: Revamp support for changing unit by typing. (39303)
  • Move HeadinglevelDropdown to its own component. (46003)
  • Button: Introduce size prop (51842)

Block Editor

  • List View: Try showing blocks that are dragged (no longer hide them). (51724)
  • Updated unstyled Button hover selector to change fill of svg and path element. (50819)
  • Writing Flow: Allow Escape key to deselect blocks and selection during multiselection. (48904)
  • Change โ€œCopy blockโ€ to โ€œCopyโ€. (51532)
  • Limit Copy/Paste Styles menu item. (51503)
  • Force disable suggestions until URLURL A specific web address of a website or web page on the Internet, such as a websiteโ€™s URL www.wordpress.org field is dirty in Link Control. (51354)
  • Top toolbar: Refine the icons on the right. (51735)
  • Improve LinkControl Edit UI. (51712)

Block Library

  • List block: Add numbering type selection. (51186)
  • Patterns: Removes the pattern experiment. (51719)
  • Remove accordion from details block keywords. (51597)
  • Add init modules to details and post-time-to-read blocks. (51606)
  • Improve logic in render_block_core_template_part. (50636)
  • Indicate Draft status of menus in Nav block menu selector. (51427)
  • Mobile โ€“ Image block โ€“ Fix issue with set width and height images. (51463)
  • Navigation: Remove destructive colors from modal. (51691)
  • Pass the block to the onGoToPage function. (51699)
  • Post Author โ€“ donโ€™t show 0 in inspector controls. (51345)
  • Remove anchor support from dynamic blocks. (51288)
  • Site Tagline Block: Remove unnecessary square path from block icon SVG. (51611)
  • Add image block aspect ratio control (51545)
  • Updating social link attributes (51997)

Accessibility

  • Autocomplete: Announce results to screen readers when first becoming visible. (51018)
  • List View: A11YAccessibility 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) focus enhancements for edit-site based on modifications to edit-post. (51404)
  • Add a description key to theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. style variations. (45242)
  • Focus first focusable on Link UI. (51105)
  • BlockLockModal: restore focus on fallback toolbar button when original button is not rendered (51666)
  • Site Editor Sidebar: improvements to buttons (51762)

Interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.

  • Add missing tests for the Image block. (51305)
  • Image block: Add animation toggle to lightbox behavior. (51357)

Global Styles

  • Accept transforms in gutenberg_get_global_styles context params. (50484)
  • Split styles menus in revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. and everything else. (51318)

Icons

  • Tweak icons for improved HiDPI devices. (51511)

Templates API

  • Return post modified datetime in response. (51362)

List View

  • Style Book: Close list view when opening the style book. (50438)

Design Tools

  • List View: Add an indicator of when a position type is set for a block. (49122)
  • Sticky Position: Try re-enabling non-root sticky position. (49321)
  • Clarify error message if duotone color values is incorrect. (51397)
  • List all the font families and font sizes from all the theme.json origins in the font picker. (51488)

Post Editor

  • Adjust the name of the custom fieldCustom Field Custom Field, also referred to as post meta, is a feature in WordPress. It allows users to add additional information when writing a post, eg contributorsโ€™ names, auth. WordPress stores this information as metadata. Users can display this meta data by using template tags in their WordPress themes. button labels. (47407)
  • Block manager: Display a โ€˜Resetโ€™ button when blocks are hidden to quickly enable all. (51200)

Media

  • Prepublish: Suggest uploading external images. (46014)

Patterns

  • Block Options: Use consistent capitalization on template parts and patterns. (51761)

CSSCSS Cascading Style Sheets. & Styling

  • Update editor UI modal width. (51733)

Commands

  • Add commands to access template, template parts and styles. (51501)
  • Add global styles related commands. (51637)

Themes

  • Block Theme Previews: Change the URL query string for more safety. (51312)
  • Update the Save Button label when youโ€™re previewing a theme. (51361)
  • Ensure there is always a Navigation available in the browse mode sidebar via fallback algorithm 50321

Bug Fixes

Block Library

  • Fix navigation error in library. (51589)
  • Fix site editor rendering of Categories block. (51329)
  • Gallery block โ€“ Add default value for innerBlockImages. (51443)
  • Latest posts: Make more link consistent between frontend and editor. (51190)
  • Navigation: Donโ€™t interfere with pointer events. (51378)
  • Post editor: Make the Post Content block available as a child of the Query block. (51405)
  • Search Block: Fix problem with buttons not outputting primary status. (51529)
  • Try providing a non-zero value for client width in image editor. (51285)
  • Query 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: Properly initialize and update perPage when we inherit from global query. (51641)
  • AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. Itโ€™s usually a square box that appears next to the userโ€™s name. block: Fix not 1:1 between the editor and the front-end. (49963)
  • Spacer block: Fix 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. markup when set to fill. (51317)
  • Buttons Block: add support for orientation-based block movers (51831)
  • Rename navigation fallback classes from WP_ to Gutenberg_ (51959)

Commands

  • Show pages with any status in the command center. (51324)
  • Add manage all custom patterns command (51845)
  • Add another batch of commands to the site editor (51832)
  • Add UI commands to the post editor (51900)
  • Add preferences and keyboard shortcuts commands (51862)

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Data

  • Core Data: Fix ESLint warning for the โ€˜useEntityRecordโ€™ hook. (51562)
  • useEntityRecord: Fix destructure error when enabled option is false. (51534)

Block Editor

  • Fix blocks autocompleter โ€˜rootClientIdโ€™ selector. (51673)
  • Inserter: Fix arrows in RTL mode. (51622)
  • Link Format: Donโ€™t return focus on the selected text โ€˜onFocusOutsideโ€™. (51684)
  • ListView: Update drop indicator line positioning to support rtl languages. (51284)
  • Page Content Focus: Default insertion point to the Post Content block. (51773)

Site Editor

  • Add โ€˜Edit templateโ€™ and โ€˜Back to pageโ€™ commands. (51364)
  • Fix template display in page details with a custom template. (51638)
  • Page details: Fix displaying slugs with non-latin characters. (51679)
  • Prevent block overlay on blocks with a โ€˜contentOnlyโ€™ editing mode. (51780)
  • Fix gradient background color repeats. (51374)
  • Global styles: Fix back button tooltip. (51725)
  • Site editor header: Fix document title back and shortcut color contrast. (51442)
  • Site editor sidebar: Fix the heading hierarchy. (51696)
  • Disable the revision button if there is no clickable menu 51851
  • Library: Fix misalignment of description in custom template parts 51868
  • Library: Fix delete shortcut incorrectly bound to non-user patterns 51830
  • Fix toolbar overlap in site editor 51810
  • Increase space between page 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. and details section 51858
  • Fix missing MenuGroup segment in Site Editor header more menu 51860
  • Update the add template modal design 51806
  • Update text color of site editor menu item hover/active states 51847
  • Fix library command path 51837
  • Restore sidebar in focus mode on Pattern click through in Browse Mode Library 51897

Accessibility

  • Distraction Free: Avoid focus loss when enabling/disabling distraction free mode via the more menu. (51627)
  • Library: Add an explicit label to the search control. (51781)
  • Site editor: Add a navigable region for content area of Library and Template views. (51782)
  • Fix shift+tab behavior to move to toolbar when the preceding block has a form element. (51548)

Global Styles

  • Color Panel: Fix rendering of tabs with no color. (51498)
  • Remove custom padding on style revisions button. (51269)

Components

  • MediaPlaceholder: Fix position of URLPopover. (51363)
  • Popover: Allow legitimate 0 positions to update popover position. (51320)
  • Button: Remove unnecessary margin from dashicon. (51395)
  • Keep framer-motion from updating minor version 51894
  • ConfirmDialog: Fix affirmative action being triggered an extra time when selecting a button via keyboard 51730
  • Tweak more icons for high-resolution devices 51768
  • ZStack: fix component bounding box to match children 51836

Patterns

  • Library: Reinstate sidebar navigation menu editing for template parts. (51825)

Interactivity API

  • Image block: Remove Lightbox markup if it is set as disabled. (51692)

Block Locking

  • Fix regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in selectors. (51541)

Typography

  • Fluid typography: Custom font-sizes should use max viewport width. (51516)

Widgets Editor

  • Fix fixed toolbar in customize widgets. (51092)
  • Hide the hidden navigation block. (50662)

Block Variations

  • [Block Library โ€“ Post Terms]: Custom taxonomies do not show icons when transforming from the toolbar. (51476)

Page Content Focus

  • Switch to Page panel when deselecting a block 51881
  • Donโ€™t show โ€˜Back to pageโ€™ notification when navigating away from page 51880
  • useBlockSync(): Reset inner blocks when component unmounts 51783
  • Fix black pixel appearing when block toolbar is empty 51779
  • Only show Page Content Focus commands when in edit mode 51888

Performance

Site Editor

  • Edit Site: Add a loading timeout. (51049)
  • Improve DocumentActions performance. (51432)
  • Prevent BlockBreadcrumb from re-rendering unnecessarily when typing. (51628)
  • Reduce number of List View re-renders while typing. (51518)
  • Improve PagePanels performance. (51319)

Block Editor

  • Improve getBlockEditingMode() and useAppender() performance. (51675)

Experiments

Global Styles

  • Color Randomizer: Fix an error when the theme has no color palette. (51539)

Documentation

  • Docs: Fix incorrect import of useEntityRecords in code example. (51630)
  • Fix broken links in editor documentation. (51321)
  • Fix grammar in the Create a Block > WordPress PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. page. (51663)
  • Fix grammar on the Create a Block tutorial page. (51662)
  • Fix grammar on the Getting Started page. (51661)
  • Update broken link. (41758)
  • Update components README.md. (51557)
  • Update wp-env changelog. (51614)
  • Updated getEntityRecord doc by using selector instead of dispatch. (51298)

Code Quality

General

  • Adopt lock-unlock.js and private-apis.js convention. (51322)
  • Formats: Avoid rerendering language edit component when typing. (51440)
  • Keyboard Shortcut: Clean up shortcut names. (51739)
  • Lodash: Refactor away from _.kebabCase() in block editor. (51687)
  • Lodash: Refactor away from _.mergeWith(). (51483)
  • Lodash: Remove from blocks package. (51703)
  • Remove pattern directory categories endpoint. (51340)
  • Require relocated class files for back-compat in WordPress releases. (51670)

Block Library

  • Add tests for WP_Classic_To_Block_Menu_Converter class. (51410)
  • Details: Set โ€˜clientIdโ€™ as useSelect dependency. (51634)
  • Move Navigation fallback files to 6.3 directory. (51572)
  • Navigation: Fix ListView deprecation notice. (51094)
  • Navigation: Just a simple refactor. (51382)
  • Remove legacy isTopLevelLink attribute from Navigation block tests. (51759)
  • Search Block: Write โ€œButton Onlyโ€ label in sentence capitalization. (51629)

Site Editor

  • Browse Mode: Move CSS to more generic selector. (51547)
  • DRY up ContentBlocksList and BlockInspectorLockedBlocks. (51281)
  • Edit Site: Refactor the NavigationMenuContent component and fix the deprecation notice. (51469)
  • PageContent: Fix unlock import. (51360)
  • Refactor Site Editor block editor code. (51524)

Block Editor

  • Lodash: Replace _.mergeWith() with deepmerge in blocks. (50637)
  • useInsertionPoint: Add missing dependency for useCallback. (51682)
  • Block Editor: Improve data selector for BlockQuickNavigationItem. (51429)
  • Block Editor: Remove redundant memoization from โ€˜ImageURLInputUIโ€™. (51658)
  • Block Editor: Simplify filtering condition for getBlockParentsByBlockName selector. (51439)
  • Block Editor: Remove unused selectors. (51674)
  • Extract nav editor component in Nav in Browse mode. (51436)
  • Remove custom button and (conditionally) show single menu on Navigation route in Browse Mode. (51565)

Design Tools

  • Fluid typography: Add missing changelog from #51516. (51668)

Layout

  • Move layout definitions out of theme.json. (50621)
  • Try stabilising layout and its associated APIs. (51434)

Global Styles

  • Global styles revisions: Move from experimental to 6.3. (51474)

Post Editor

  • Fix refactor flat term selector to use data api for creating new terms. (50952)

Data Layer

  • Private actions and selectors: Return stable references, expose to thunks. (51051)

Themes

  • Block Theme Previews: Rename GET variable and prepare for core compat. (51738)

Interactivity API

  • Remove the hydration console log of the Interactivity API. (51571)
  • Use interactivity API for Navigation and File blocks only in Gutenberg. (51694)
  • Behaviors: Move behaviors code to experimental folder. (51654)

Components

  • Convert ClipboardButton to TypeScript. (51334)
  • Use internal context system to apply toolbar variant to toolbar dropdowns. (51154)

Parser

  • Split each class in parser.php to a separate file. (48693)

Tools

Testing

  • Add โ€˜Mamadukaโ€™ as one of the code owners for Playwright tests. (51470)
  • Combine Site Editor list view tests into a single file. (51635)
  • Consolidate duplicate block tests. (51352)
  • Fix flaky โ€˜Keep styles on block transformsโ€™ end-to-end test. (51593)
  • Fix flaky โ€˜Push to Global Stylesโ€™ end-to-end test. (51636)
  • Fix flaky โ€˜Switch to Draftโ€™ action in preview end-to-end tests. (51564)
  • Fix flaky โ€˜hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. APIโ€™ end-to-end test. (51592)
  • Fix flaky Image block interactivity end-to-end test. (51573)
  • Fix the flaky site editor list view tests. (51598)
  • Migrate โ€˜Allowed Blocks Setting on InnerBlocksโ€™ tests to Playwright. (51677)
  • Migrate block hierarchy navigation tests to Playwright. (51517)
  • Playwright Utils: Change preference update method in setIsFixedToolbar. (51659)
  • Playwright Utils: Simplify editor preference updates in createNewPost. (51560)
  • Styles Navigation Screen: Close style book using location. (51365)
  • Update BlockEditorProvider tests. (51497)
  • Update E2E test sharding on CI, make Playwright tests faster, Puppeteer tests slower. (50362)
  • Update the โ€˜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. blockโ€™ test and fix flakiness. (51631)
  • end-to-end tests: Try fixing โ€˜networkidleโ€™ timeout errors. (51826)
  • test: Re-enable native integration tests. (51706)
  • Migrate Navigable toolbar test to Playwright. (51514)
  • Mobile unit tests: Remove custom waitFor implementation. (46735)
  • Set fixedToolbar to false after each top toolbar test to ensure proper cleanup. (51600)
  • Fix performance test failure on trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. (51407)
  • Performance tests: Make theme versions consistent cross-env. (50905)
  • Performance tests: Update base point to compare. (51381)

Build Tooling

  • Babel config: Enable useSpread option for JSX transform to reduce transpilation. (51574)
  • Lodash: Remove from lint staged type check. (51698)
  • Performance Tests: Update the base point to compare against. (51689)
  • wp-env: Try to fix failing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 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/ actions. (51513)
  • npm lockfile: Hoist reakit and date-fns packages to the top. (51500)

Plugin

  • Add script to compile usage of experimental APIs. (51341)
  • Remove Details block setting field from the experiments page. (51372)

Contributors

First time contributors merged the following PRs for 16.1 ๐ŸŽ‰:

The following contributors also merged PRs in this release:

@aaronrobertshaw @afercia @alexstine @andrewserong @aristath @artemiomorales @aurooba @bangank36 @c4rl0sbr4v0 @carolinan @ciampo @dcalhoun @derekblank @diegohaz @draganescu @ellatrix @fabiankaegy @fluiddot @geriux @getdave @glendaviesnz @jameskoster @jasmussen @jeryj @jhnstn @jsnajdr @juanfra @kozer @luisherranz @MaggieCabrera @Mamaduka @matiasbenedetto @mcliwanow @mcsf @mikachan @n2erjo00 @noahtallen @noisysocks @ntsekouras @oandregal @okmttdhr @paulopmt1 @pbking @peterwilsoncc @pooja-muchandikar @ramonjd @richtabor @samnajian @SantosGuillamot @SavPhill @SaxonF @scruffian @shimotmk @Sidsector9 @SiobhyB @spacedmonkey @stokesman @sunyatasattva @t-hamano @talldan @tellthemachines @tyxla @walbo @WunderBart @xerpa43 @youknowriad @priethor @ajlende @mirka

Mega props to @jameskoster and @joen for the visual assets, @priethor for peer review, and @isabel_brison for helping get the release published to 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/.

Thank you to everyone who was involved. And to those reading this post ๐Ÿ˜€


Reminder: โ€œWhatโ€™s new inย Gutenbergโ€ฆโ€ posts (labeled with theย #gutenberg-new tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are posted after every Gutenberg release. Learn more about how to keep up to date with news about Gutenberg and the Site Editor project (formerly calledย Full Site Editing).

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

Dev Chat agenda, June 28, 2023

The next weekly WordPress developers chat will take place onย Wednesday, June 28, 2023 at 20:00 UTC ย in theย core channel ofย Make WordPress Slack. All are welcome.

1. Welcome and housekeeping

Summary from Dev Chat, June 21, 2023

2. Announcements

WordPress 6.3 Beta 1 has been postponed to June 28, 2023 โ€“ check the post and the ย #6-3-release-leadsย channel for updates.

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/ 16.1 update

3. Highlighted posts

A Week in Core โ€“ June 26, 2023 โ€“ props to @audrasjb for pulling together.

Highlights onย TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ย between June 19 and June 26, 2023, starting with 37 new contributors!

  • 112 commits
  • 192 contributors
  • 68 tickets created
  • 16 tickets reopened
  • 107 tickets closed

Lots of exciting commits and progress on tickets across the different coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channels. A shout out to everyone involved, and those working on 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. for 6.3 in general.

WP Feature Notifications: Request for Feedback on Admin Notices, June 24, 2023. Thereโ€™s a survey on the post to give feedback on the current system of notices within the WordPress dashboard.

4. Forthcoming release updates

Some of the links in this section act as reminders or to help new contributors. To allow for greater discussion on tickets/ blockers for 6.3, not all these links may be re-shared in the dev chat itself.

6.3 โ€“ next major WordPress release

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ย on 6.3 with:

6.4

WordPress 6.4 Development Cycle

5. Tickets or Components help requests

Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, donโ€™t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed. Tickets for 6.3 will be prioritized.

6. Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

For awareness, there is a discussion on GitHub for a name for the Command Center introduced in Gutenberg 15.6 under the experimental flag.

#6-3, #agenda, #dev-chat

Dev Chat Summary: June 21, 2023

The notes from the weekly WordPress developers chat which took place on Wednesday June 21, 2023 in the core channel of Make WordPress Slack.

Key links

Announcements

Proposal: Criteria for Removing โ€œBeta Supportโ€ from Each PHP 8+ Version: This proposal published on June 20 sets criteria for determining when WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has reached compatibility with a specific PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version that WordPress supports, and a phased process for removal of the โ€œ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. supportโ€ label and beyond. A big Thanks to the contributors who have been working on this proposal. Community feedback can be added to the post comments.

@ironprogrammer: This is a big deal, and open for community discussion.

Highlighted posts

A Week in Core โ€“ June 19, 2023 โ€“ Props to @audrasjb for pulling this together! Changes on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between June 12 and June 19, 2023:

  • 41 commits
  • 61 contributors
  • 66 tickets created
  • 7 tickets reopened
  • 40 tickets closed
  • and 9 new contributors in this period!

Whatโ€™s new in Gutenberg 16.0? (14 June): Gutenberg 16.0 is now available for download from the plugins repository.

FSE Program Testing Call #24: Momery Makeover: Join in on this #fse-outreach-experiment, which will be closed for additional comments on June 28, 2023.

Whatโ€™s new for developers? (June 2023) from the Developer Blogblog (versus network, site). The latest updates are focused around 6.3.

Updates on forthcoming releases

WordPress 6.3 โ€” 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.

Upcoming: Beta 1 for the 6.3 release is next Tuesday, June 27, 2023 (updated, this will be June 28, 2023).

Update from @francina and @priethor, release coordinators for WordPress 6.3. Francesca shared:

  • tasks looking at for week leading to Beta 1
  • the moving parts are being coordinated in theย #6-3-release-leadsย channel
  • two discussions in the 6.3 release leads channel in the last couple of weeks:
    • one is about โ€œblessingโ€ to merge from 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/ to Core. Start from Slack message. In the threads there are multiple conversations happening, also related to the 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/ or can be cost-based plugin from a third-party. stats. She encourages everyone to read and asย @jeffpaul suggested a proposal on the Make/Core blog is always a great conversation starter to have a wider diversity of opinions.
    • the other one is aboutย Trac Ticketticket Created for both bug reports and feature development on the bug tracker. #12009
  • we are approaching Beta 1, which means now is the time to make hard decisions that in some cases might be disappointing for some. Itโ€™s part of the process. Francesca encouraged people to read about the items and find out about how decisions are made or not in the open transparent process WordPress follows.

6.3 dev notes tracking issue is out. If you can help docs in the release, do let them know.

6.3 Editor tasks board on GitHubย โ€“ contactย @ndiegoย to take one of these 6.3 tasks from the board.

Bug scrub schedule for 6.3

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ย on 6.3 with:

6.4

WordPress 6.4 Development Cycle

Help requests on tickets/ Components

@oglekler encouraged contributors to view and comment on tickets updated at 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. Europe 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/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, especially by first time contributors. She suggested using the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. modified between 8th and 9th of June 2023. She suggested exploring adding a mark, keyword or creating a list of such tickets at future Contributor Days.

@presskopp added encouragement for good first bugs and highlighted discussion on Slack on releases focused on fixing bugs.

Open Floor

No further items.

#6-3, #dev-chat, #summary

WordPress 6.3 Beta 1 postponed

The WordPress 6.3 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 is postponed 24 hours due to an unexpected error found during the testing phase of the release part, as styles in wp-admin are not loading unless SCRIPT_DEBUG is set to true. Contributors are investigating the issue at hand, and the release party will be resumed once fixed, tentatively on June 28th at 17:00 UTC in #core.

The cycle page has been updated accordingly.

Thanks to the community effort in testing new versions, this error was spotted early on. Thank you for your patience and continuous commitment to making WordPress!


Props to @annezazu, @audrasjb, @azaozz, and @dansoschin for the peer review.

#core #6-3

Performance Chat Summary: 27 June 2023

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members ofย #core-performance
  • 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 for the 6.3 release is today!

Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @aristath

Database Optimization

Link to roadmap projects

Contributors: @aristath @spacedmonkey @olliejones

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a userโ€™s browser. https://www.javascript.com & CSSCSS Cascading Style Sheets.

Link to roadmap project

Contributors: @mukesh27 @10upsimon @adamsilverstein @westonruter

  • @joemcgill Iโ€™m happy to be able to report that I committed the PR forย https://core.trac.wordpress.org/ticket/12009ย yesterday, closing a 13 year old ticketticket Created for both bug reports and feature development on the bug tracker.. This is a big milestone for the team, thank you to everyone who contributed to get this across the line. I know that there is still a desire to extend support to inline scripts, so Iโ€™ve opened a new ticket (https://core.trac.wordpress.org/ticket/58632) for that discussion.
  • @10upsimon is drafting a dev-note for this change, which we can hopefully post in the next few weeks.
  • @spacedmonkey I had people asking me questions about module support. โ€“ย https://core.trac.wordpress.org/ticket/56313ย I wonder if this should be something we look into for WP 6.4
    • @joemcgill Seems like the logical next step. Would be nice to do in coordination with packages from 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/ that want to make use of it.
    • @flixos90 Yeah I know the folks working on the new interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. were quite interested in this one
    • @clarkeemily letโ€™s look at adding this to our roadmap in a future chat
    • @spacedmonkey The important thing about this functionality is the developer communication. We need a great 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., with easy to understand and copy and paste implementations. We will also have to show developers how we can make the change and be backwards compatible.

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill

  • @flixos90 Excited to share that yesterday we landedย fetchpriority="high"ย support:ย https://core.trac.wordpress.org/changeset/56037
    • That commit includes notable refactoring to make the logic that was previously scoped to only lazy-loading more broadly available, as it is also required forย fetchpriority
    • So with that refactoring it also unblocks a fix to another issue that still needs to be addressed with lazy-loading:ย https://core.trac.wordpress.org/ticket/58635
    • Iโ€™m planning to work on 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. for these changes. Still thinking through whether it should be two individual dev notes or a single one. While they are separate topics, they are deeply intertwined, and especially with the refactoring it may be a lot of repetition to have two separate posts

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @olliejones @joemcgill @mukesh27

  • @joemcgill Nothing here either. Though, once the dust settles on beta release day, Iโ€™d like to revisit improvements we can make to the automated testing tools during this release cycle, to better support the 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). cycle.

Ecosystem Tools

Link to roadmap projects

Contributors: @joegrainger @mukesh27

  • @mukesh27 and @joegrainger are currently prioritizing tasks for Milestone 2 of theย Plugin Checker. Progress can be seen on theย GitHub repoย here. Feel free to take a look and leave any thoughts/ideas you may have in the repo. Thanks!

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

  • @flixos90 Still awaiting approval of the Dominant Color Images pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. in the plugin repo

Open Floor

  • @clarkeemily ourย next chat is on July 4 Independence Day in the US, so I suspect a large portion of folks will be out. I still plan to run the chat, but a heads up that it will likely be much shorter as many folks will be out
  • @mukesh27 highlighted the message from @johnbillion
    • #21938ย has been re-opened with the performance focus added, the e2e tests are indicating a potential performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. that needs testing in different browsers and configurations
    • @johnbillion Ah yes ^ . Some of you might have seen the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Gutenberg e2e tests are flakier than usual at the moment and it may be due to theย no-storeย cache 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. directive that was added last week. Iโ€™ve reopened the ticket and added the performance focus, if anyone has time to do some testing that would be greatly appreciated.
    • @joemcgill I remember looking at this last week when I opened 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. ticket about the E2E tests, and I was not convinced that the failures were related to that change, so this might be a red herring. I recall seeing several instances of networknetwork (versus site, blog) timeouts showing up prior to that change.
    • @johnbillion I agree it could be a red herring, but git bisect does point to that commit, so Iโ€™m honestly not sure. Although the core e2e tests did start failing before that commit, so..
    • @joemcgill I think we can certainly try revering that change to see if the tests stop failing. Are there other steps to take to try and debug this issue?
    • @johnbillion I added some testing steps in a comment on the ticket, I donโ€™t have much else at the moment
  • @westonruter On another front, I believe Iโ€™ve addressed the last code review for optimizing the emoji loader. Final reviews/testing appreciated so I can commit in the next hour:ย https://github.com/WordPress/wordpress-develop/pull/4562

Our next chat will be held on Tuesday, July 4, 2023 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Performance Chat Agenda: 27 June 2023

Here is the agenda for this weekโ€™s performance team meeting scheduled for June 27, 2023 at 15:00 UTC.


This meeting happens in the #core-performance channel. To join the meeting, youโ€™ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

A Week in Core โ€“ June 26, 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 June 19 and June 26, 2023.

  • 112 commits
  • 192 contributors
  • 68 tickets created
  • 16 tickets reopened
  • 107 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. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • Add the no-store and private directives to the Cache-Control 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. when preventing caching for logged in users โ€“ #21938, #57627
  • Backwards compatibility for new sortable keys โ€“ #32170
  • Consistent positioning and size of search form โ€“ #57949
  • Fix password layout for RTL and mobile โ€“ #9883
  • Fix visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in media search input โ€“ #57949
  • Hide password in options/writing โ€“ #9883
  • Make checkbox column clickable โ€“ #21516
  • Reduce translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. calls after [55969] โ€“ #57675
  • Replace Tagline option placeholder with a description โ€“ #57675
  • Replace contracted verb forms for better consistency โ€“ #30796
  • Set accessible state for list table headers โ€“ #32170

Bootstrap/Load

  • Require wp-includes/compat.php earlier in wp-settings.php โ€“ #58206
  • Require wp-includes/compat.php in wp-load.php โ€“ #58206

Build/Test Tools

  • Store artefacts of failing E2E test runs โ€“ #58596
  • Update URLURL A specific web address of a website or web page on the Internet, such as a websiteโ€™s URL www.wordpress.org of theme unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. data โ€“ #58569
  • Update the test for pre_wp_setup_nav_menu_item filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. โ€“ #56577

Bundled Themes

  • Twenty Fifteen: Fix Letter Case implementation โ€“ #58526
  • Twenty Fifteen: Remove IE specific resources โ€“ #56699
  • Twenty Fourteen: Fix Letter Case implementation โ€“ #58526
  • Twenty Nineteen: Always set background color and foreground color together โ€“ #45916
  • Twenty Nineteen: Ensure Separator 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. supports theme colors in editor โ€“ #58558
  • Twenty Nineteen: Fix a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. coding standard issue found after [55970] โ€“ #46474
  • Twenty Nineteen: Prevent a console error related to the main navigation on Firefox โ€“ #46474
  • Twenty Nineteen: Remove unused function parameters and variables โ€“ #57397
  • Twenty Nineteen: Revert [55960] โ€“ #45916
  • Twenty Seventeen: Make twentyseventeen_is_static_front_page() an alias of twentyseventeen_is_frontpage() โ€“ #43515
  • Twenty Seventeen: Remove IE specific resources โ€“ #56699
  • Twenty Sixteen: Fix Letter Case implementation โ€“ #58526
  • Twenty Sixteen: Fix List block padding in the editor โ€“ #58409
  • Twenty Ten: Improve Pullquote block line height for better readability โ€“ #52546
  • Twenty Thirteen: Remove IE specific resources โ€“ #56699
  • Twenty Thirteen: Remove an unnecessary border from Table block โ€“ #56538
  • Twenty Twenty-Two: Add missing subject tags and feature tags โ€“ #58437
  • Twenty Twenty: Fix Letter Case implementation โ€“ #58526
  • Twenty Twenty: Fix an RTL style issue leading to failed Test Default Themes & Create ZIPs workflow โ€“ #58396
  • Twenty Twenty: Fix left margin in Latest Posts & Latest Comments blocks โ€“ #58396
  • Twenty Twenty: Inherit Quote blockโ€™s paragraph custom letter spacing in the editor โ€“ #58033
  • Twenty Twenty: Remove various unused function parameters and variables โ€“ #57371
  • Twenty Twenty: Revert [56034] pending further investigation โ€“ #58396

Cache 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 unused usermeta global cache group โ€“ #58175

Code Modernization

  • Replace usage of strpos() with str_contains() โ€“ #58206
  • Replace usage of substr() with str_starts_with() and str_ends_with() โ€“ #58220
  • Use str_contains() in a few more places โ€“ #58206
  • Use str_contains() in a few more places โ€“ #58206
  • Use str_contains() in a few more places โ€“ #58220
  • Use str_ends_with() in a few more places โ€“ #58220
  • Use str_starts_with() and str_ends_with() in a few more places โ€“ #58220
  • Use str_starts_with() and str_ends_with() in a few more places โ€“ #58220
  • Use str_starts_with() in WP_Theme_JSON class methods โ€“ #58012

Coding Standards

  • Fix missing semicolon after [56009] โ€“ #40966
  • Fix undeclared variable issue โ€“ #40966
  • Use Yoda condition in str_ends_with() โ€“ #58220
  • Use strict comparison in wp-includes/pomo/translations.php โ€“ #57839

Database

  • Replace str_contains() and str_ends_with() usage in wpdb methods โ€“ #58206

Docs

  • Add missing param description to update_menu_item_cache in wp_get_nav_menu_items() โ€“ #58468, #57840
  • register_block_style() docblockdocblock (phpdoc, xref, inline docs) improvement โ€“ #58562, #57840

Editor

  • Add a description key to theme.json style variations โ€“ #58614
  • Add no-js fallback for site editor โ€“ #56228
  • Fix block editor styles being registered with frontend stylesheets โ€“ #58605
  • Fix block template utils test: use template part instead of template object โ€“ #58540
  • 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) of new custom fieldCustom Field Custom Field, also referred to as post meta, is a feature in WordPress. It allows users to add additional information when writing a post, eg contributorsโ€™ names, auth. WordPress stores this information as metadata. Users can display this meta data by using template tags in their WordPress themes. UIUI User interface โ€“ #15631
  • Introduce WP_Theme_JSON::prepend_to_selector() to improve code quality and performance โ€“ #58193, #58457
  • Register core block styles in one place โ€“ #58528
  • Rename wp_get_remote_patterns to wp_get_theme_directory_pattern_slugs โ€“ #58460
  • Use static closures to avoid memory leaks โ€“ #58323
  • `wp_get_global_styles`: allow transforming the CSSCSS Cascading Style Sheets. Custom Properties into the values they represent โ€“ #58588
  • `wp_get_global_styles`: return the standard format for CSS Custom Properties โ€“ #58467
  • add Post Content attributes to block editor settings โ€“ #58534
  • add grid layout type โ€“ #58554
  • add grid layout type โ€“ #58554
  • add support for block-level link hover colors โ€“ #58575
  • add text columns to typography support โ€“ #58549
  • fix site editor layout 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. โ€“ #56228
  • rename reusable blocks to patterns โ€“ #58577
  • revert add grid layout type โ€“ #58554
  • update layout classnames and specificity โ€“ #58548
  • use layout.wideSize as max viewport width โ€“ #58522
  • use logarithmic scale for fluid typography โ€“ #58523

Embeds

  • Add Anghami as a trusted oEmbed provider โ€“ #49850

Filesystem API

  • Attempt to create directory in copy_dir() โ€“ #41855

General

  • Introduce WP_DEVELOPMENT_MODE constant to signify context-specific development mode โ€“ #57487
  • Replace substr_compare() usage in the str_ends_with() polyfill โ€“ #58220
  • Replace some instances of โ€œblogblog (versus network, site)โ€ with โ€œsiteโ€ in documentation, translator comments, and user-facing text strings โ€“ #58117
  • Return early from str_ends_with() polyfill if both haystack and needle are empty โ€“ #58220
  • fix overridden typos โ€“ #58464

Help/About

  • Improve Dashboard screen options behavior on small screens โ€“ #57977

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

  • Ensure determine_locale() does not potentially return an empty string โ€“ #58317

KSES

  • Add support for CSS repeat() function โ€“ #58551

Login and Registration

  • Add required to Username/password inputs โ€“ #32510

Media

  • Automatically add fetchpriority="high" to hero image to improve load time performance โ€“ #58235
  • Display the โ€œCopy URLโ€ and โ€œDownload fileโ€ row actions when the โ€œUnattachedโ€ filter is applied โ€“ #57890, #57893
  • Redirect deprecated wp-admin/media.php file โ€“ #57612

Posts, Post Types

  • Add a $previous_status parameter to wp_trash_post() related hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. โ€“ #58392

Quick/Bulk Edit

  • Donโ€™t set publish date when editing drafts โ€“ #19907

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/

  • Indicate when a theme supports the Site editor in the Themes REST API response โ€“ #58123
  • Return post modified datetime for Templates โ€“ #58540

Script Loader

  • Add support for HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. 5 โ€œasyncโ€ and โ€œdeferโ€ attributes โ€“ #12009
  • Replace str_contains() usage in wp-includes/script-loader.php โ€“ #58206

Themes

  • Allow non-block themes to add theme support for border settings โ€“ #58598
  • Allow non-block themes to add theme support for link color settings โ€“ #58597
  • Change the order of path check in is_block_theme method โ€“ #58520
  • Fix caching issue in get_post_templates method in WP_Theme โ€“ #57886

Tools

  • Fix unresolvable conflicts computation in package sync script โ€“ #58628

Upgrade/Install

  • Add aria-describedby for input descriptions โ€“ #58613
  • Move location of $upgrade_notice for better consistency โ€“ #57939
  • Prevent users from sending multiple bulk pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. updates โ€“ #40966
  • Show/hide toggle on password fields โ€“ #3534
  • Update โ€˜show detailsโ€™ button change โ€“ #44714

Props

Thanks to the 192 (!!) people who contributed to WordPress Core on Trac last week:

@sabernhardt (28), @audrasjb (21), @mukesh27 (20), @costdev (19), @spacedmonkey (16), @joedolson (14), @oglekler (13), @ramonopoly (11), @sergeybiryukov (11), @poena (10), @peterwilsoncc (8), @azaozz (8), @swissspidy (8), @flixos90 (8), @afercia (6), @tb1909 (5), @isabel_brison (5), @andrewserong (5), @dd32 (5), @zunaid321 (5), @kebbet (5), @joemcgill (5), @thakordarshil (4), @pateljaymin (4), @ugyensupport (4), @panchalhimani711 (4), @nidhidhandhukiya (4), @desrosj (3), @westonruter (3), @neychok (3), @pooja1210 (3), @ironprogrammer (3), @nihar007 (3), @clorith (3), @alexstine (3), @rutviksavsani (2), @karmatosed (2), @pbiron (2), @soulseekah (2), @hellofromtonya (2), @bgoewert (2), @kafleg (2), @Cybr (2), @ryelle (2), @samnajian (2), @Soean (2), @jane (2), @upadalavipul (2), @thekt12 (2), @dhruvishah2203 (2), @NekoJonez (2), @wpnook (2), @oandregal (2), @timothyblynjacobs (2), @10upsimon (2), @kapilpaul (1), @ignatggeorgiev (1), @jorbin (1), @krupalpanchal (1), @tacoverdo (1), @ramonopoly (1), @aristath (1), @maxcgparis (1), @rianrietveld (1), @bor0 (1), @boniu91 (1), @renyot (1), @kjellr (1), @zgrkaralar (1), @sabreuse (1), @wojtek.szkutnik (1), @pamprn09 (1), @brookedot (1), @ryan (1), @denis-de-bernardy (1), @mastrup (1), @jrf (1), @otto42 (1), @williampatton (1), @maniu (1), @hellofromTonya (1), @johnjamesjacoby (1), @dimijazz (1), @laurelfulford (1), @samful (1), @monzuralam (1), @azizantoun (1), @bacoords (1), @allancole (1), @d-signed (1), @nant82 (1), @sanchothefat (1), @matmoe (1), @ronakganatra (1), @jeremyfelt (1), @aznadesign (1), @mitchoyoshitaka (1), @lessbloat (1), @ogleker (1), @Boniu91 (1), @dilipbheda (1), @joostdevalk (1), @luehrsen (1), @ianbelanger (1), @grantmkin (1), @McAlyster (1), @janpaulkleijn (1), @rehanali (1), @pavanpatil1 (1), @Dharm1025 (1), @Ankit K Gupta (1), @markdoliner (1), @ayeshrajans (1), @paulkevan (1), @andy786 (1), @johnbillion (1), @pouicpouic (1), @joyously (1), @afragen (1), @Heiko_Mamerow (1), @Denis-de-Bernardy (1), @subrataemfluence (1), @nrqsnchz (1), @fencermonir (1), @zebaafiashama (1), @rudlinkon (1), @uxtremist (1), @rfischmann (1), @youknowriad (1), @mista-flo (1), @batmoo (1), @franrosa (1), @annashopina (1), @hareesh-pillai (1), @bitnissen (1), @krupajnanda (1), @kevin940726 (1), @xkon (1), @nkeller15 (1), @mujuonly (1), @hugod (1), @davidbaumwald (1), @shailu25 (1), @harshgajipara (1), @dmsnell (1), @nadimcse (1), @glendaviesnz (1), @adamsilverstein (1), @mukeshpanchal27 (1), @mor10 (1), @scep (1), @vanaf1979 (1), @Otto42 (1), @MarcGuay (1), @bookdude13 (1), @melchoyce (1), @aaronrobertshaw (1), @adeltahri (1), @chouby (1), @Clorith (1), @ocean90 (1), @dingo_d (1), @mikeschroder (1), @dhrumilk (1), @markparnell (1), @prashantbhivsane (1), @marybaum (1), @ababir (1), @chiragrathod103 (1), @jahidcse (1), @ntsekouras (1), @ryokuhi (1), @Narthur (1), @simonemanfre (1), @intoxination (1), @vasilism (1), @xmarcos (1), @matt (1), @markjaquith (1), @nazgul (1), @akbigdog (1), @rob1n (1), @DrewAPicture (1), @MichaelH (1), @empireoflight (1), @rmccue (1), @markoheijnen (1), @r0uter (1), @amansurov (1), @bi0xid (1), @caraffande (1)

.

Congrats and welcome to our 37 (!!) new contributors of the week:ย @thakordarshil, @pateljaymin, @panchalhimani711, @samnajian, @dhruvishah2203, @wpnook, @maxcgparis, @renyot, @mastrup, @dimijazz, @azizantoun, @bacoords, @aznadesign, @McAlyster, @janpaulkleijn, @markdoliner, @Heiko_Mamerow, @fencermonir, @uxtremist, @rfischmann, @franrosa, @annashopina, @bitnissen, @shailu25, @harshgajipara, @nadimcse, @scep, @vanaf1979, @ababir, @jahidcse, @Narthur, @simonemanfre, @vasilism, @xmarcos, @akbigdog, @r0uter, @amansurov, and @caraffandeย โ™ฅ๏ธ

Core committers: @audrasjb (37), @sergeybiryukov (21), @joedolson (14), @isabel_brison (13), @peterwilsoncc (5), @flixos90 (4), @oandregal (4), @spacedmonkey (3), @swissspidy (2), @johnbillion (2), @westonruter (1), @bernhard-reiter (1), @joemcgill (1).

#6-3, #core, #week-in-core

Editor Chat Agenda: June 28th, 2023

Facilitator and notetaker:ย @ajitbohra

This is the agenda for the weeklyย editor chatย scheduled forย Wednesday, 28 June 2023 at 19:30 GMT+5:30.

This meeting is held in theย #core-editorย channel in the Making WordPressย SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

  • Announcements
  • Project updates
  • Task Coordination
  • Open Floor โ€“ extended edition.

If you are not able toย attendย the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda,ย #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor-agenda,ย #meeting, #core-editor