Bug Scrub Schedule for 5.9

With 5.9 well underway, we’re ready to schedule the 5.9 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 sessions. These 5.9 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Scrubs:

Hosted by @audrasjb

Hosted by @chaion07 (APAC-friendly)

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. Scrubs:

Focus: issues reported from the previous beta.

  • TBD

RC Scrubs:

Focus: issues reported from the previous RC

  • TBD

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 5.9 scheduled bug scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Twenty Twenty-Two Triage: Every Monday 15:00 UTC in the #core-themes 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/ Design Triage: Every Tuesday 16:00 UTC in the #design channel.
  • 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) Scrub: Every Friday 15:00 UTC in the #accessibility channel.
  • Testing Scrub: Every Friday 13:15 UTC in the #core-test channel.
  • CSSCSS Cascading Style Sheets. Scrub: First Thursday of every month 20:00 UTC in the #core-css channel.
  • Upgrade/Install Component: Every Tuesday at 17:00 UTC in the #core-auto-update channel.
  • Help/About Component: Every Monday, 20:30 UTC in the #core channel.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @audrasjb or @chaion07 on 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/. and let us know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 5.9-focused? Awesome! We’ll add it to the schedule here. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 5.9 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 5.9 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @audrasjb or @chaion07 on slack.

Thanks @jeffpaul for proof-reading.

#5-9, #bug-scrub

Dev chat summary, December 1, 2021

The agenda followed for the meeting.

The meeting was led by @marybaum and summary written by @webcommsat.

The full meeting starts at this link 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/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel

1. Welcome

2. Announcements

WordPress Beta 1 is out (30 November 2021)

3. Useful posts

4. Update on journey to 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. 2

@hellofromtonya: Beta 2 is planned for next week, 7 December 2021.

Until that time, focus shifts towards triaging, investigating, and fixing issues found in Beta 1 or just prior to it.

Issues

There are 4 issues identified during the release party and after which need contributors to help test, share feedback, investigate, and resolve:

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/

Work continues on bugs in Gutenberg too though currently not seeing blockers and progress on the list of important is proceeding well.

How can you help?

Test, Test, Test. Give feedback through a test report that shares your findings, even if it’s “can’t reproduce”.

And thank you to all contributors. Your contributions help to make WordPress.

@costdev: For test reports, you can use this template (screencast optional).

For test reports, you can use this template (screencast optional).

Just a note that the test report template is also very useful for including in the original description in a ticketticket Created for both bug reports and feature development on the bug tracker. when you’re reporting an issue.

Letting us know the environment that the issue occurs on lets us:

  • Try to reproduce using that environment
  • Try to reproduce using a similar environment
  • Try to reproduce in totally different environments

@marybaum: Thanks @hellofromtonya and @costdev. For our #Marketing and other observers, this kind of testing doesn’t require any code skill.

5. Component maintainers update

About / Help page

@webcommsat: With the beta 1, we postponed our weekly catchup to this Friday 3 December 2021, 19:00 UTC. In addition, there will be a 10 minute drop-in, facilitated by @marybaum from 18:50 UTC for those coming to shadow, observers, or new people from marketing. We will look further at the designs from @critterverse and other items on the About page and its associated items, and the start of the social media collaborations. Please join us if you can and look at the initial design draft on the ticket.

If anyone has a particular aspect to highlight for Friday, please let @marybaum and @ abhanonstopnews (on Slack) know.

More on how you can help contribute to social media promotions for the 5.9 release on the marketing blog. Everyone is welcome to join the marketing meeting next week, Wednesday 8 December 2021, at 14:00 UTC, to start exploring the social media posts too.

6. Open Floor

Q. A question asked in Marketing today, if someone finds an error on beta 1, is there a cut off for when they can report it?
A: There is no cut-off. They can report it when/ if something is found.

No other items were raised.

#5-9, #dev-chat

Performance team meeting summary – November, 30 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus groups updates

Images

@adamsilverstein gave a great update on the progress of the focus. First, all issues and ideas related to focus will be tracked in this GitHub project. This will facilitate asynchronous contributions and discussions. The top priority issue on the project is this one, for creating a WebP module, and port the code to the repository.

On top of that, the focus meeting last Thursday was a success and the team is planning to hold a next one. Keep an eye on the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site) and the #core-media channel on 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/. to keep up with the agenda.

There were also several discussions about the main projects of the focus: WebP by default in WordPress Core and 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. of existing images into the WebP format. Here are the links to the discussion pieces on Slack:

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/.

Since most of the people in this focus are deeply involved in the next release, there are no major updates at the moment.

Measurement

For this focus, there were some discussions about starting a dedicated side conversation (see thread). Currently, the team is still thinking about the best form for this conversation, chat or video call. If you have any opinions, feel free to leave a comment in the thread linked above or on this post.

Performance features development coordination

There is currently this issue on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository regarding the code infrastructure of the performance modules. This step is very important to move forward, so feel free to leave a comment or feedback on the issue.

Open Floor

Jérôme Vieilledent (@lolautruche on Slack) mentioned before the meeting that Blackfire and Platform.sh are willing to support the WordPress Performance team initiative. Blackfire might be interested in donating an account to 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/ organization for the team’s purposes. See Slack discussion here.

#meeting, #performance, #performance-chat, #summary

Dev chat agenda for December 1, 2021

Announcements

The WordPress 5.9 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 has landed, after a lot of very hard work by a lot of very dedicated contributors. Please download and test! Also, in the beta period, work pivots to focus only on bugs that have shown up since feature freeze on November 8.

WordPress 5.8.2 is also live, and you should update. Minor releases usually fix bugs and 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. vulnerabilities.

Blogblog (versus network, site) posts of note

@annezazu has published this guide to testing the FSE features.

This Editor Chat Summary from @get_dave is a good place to find the latest on 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.

@audrasjb has the latest issue of A Week in Core.

And remember that we’re on a revised release schedule.

Got other posts that should get the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team’s attention? Please add them in the comments.

Upcoming releases

The current release is version 5.9, and we are now in beta. There is much to discuss.

Component Maintainers

If you maintain a component and need help with beta fixes or other blockers as the 5.9 release moves forward, please plan to join the chat and update the group.

Open Floor

Add your topic to the comments, and enjoy priority for your topic at the beginning of Open Floor.

See you Wednesday at 20:00 UTC!

#agenda, #core, #dev-chat

Editor Chat Agenda: 1 December 2021

Facilitator and notetaker: @jorgefilipecosta

This is the agenda for the weekly editor chat scheduled for Wednesday, December 1 2021, 03:00 PM GMT+1.

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/..

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, #core-editor, #core-editor-agenda, #meeting

Editor Chat Summary: 24th November 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-11-24 14:00 UTC in Slack. Moderated by @get_dave.

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/ 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 releases

  • Gutenberg 12.0.0 was released (after the meeting) – thanks to @welcher for leading this one.
  • Highlights post will be released on Make blogblog (versus network, site) soon.

WordPress 5.9 status updates

Updates based on the scope for Site Editing projects

Updates were requested for the key projects:

Native Mobile Team

@antonisme provided the update:

Shipped

  • Added Clipboard Link Suggestion to Image 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 Buttons block
  • Added auto opening of media upload options to new Gallery block

Fixes:

  • Only set font sizes for block based themes
  • Reverted erroneous native editor package version bumps

In Progress:

  • Upgrade to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native v0.66.
  • Finalizing GSS Font size, line height and selected text colors.

@get_dave provided the update:

Components Packages

@mciampini provided an update:

Shipped

  • ToolsPanel has an improved README and Storybook stories illustrating its usage. This component is used to group related 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. controls, grouping them and providing a standard UIUI User interface for showing and hiding them. 
  • We’ve added an example for adding a chevron icon in the Item component for certain types of navigation used in Styles. 

Fixes:

  • The ZStack component’s offset prop now supports RTL languages properly.

In Progress:

Templates

@annezazu stepped in to provide an update based on her recent knowledge:

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@annezazu:

  • Update on my end — lots of testing/triaging for 5.9 in GitHub, helped ship the recent /News post highlighting a 5.9 video a crew of us worked on.
  • Continued amplifying & responding to the latest FSE outreach call for testing.
  • Shared some personal thoughts on why I voted to delay 5.9, and nearly done with draft of Styles user doc (needed for the welcome guide).
  • After this next week, I’ll have far more time to focus on documentation and testing efforts so plan to continue to shift attention there (have a presentation due this week about 5.9).

@get_dave:

@zieladam:

  • I’m helping with making the navigation block ready.
  • Right now working on giving new menus a name in https://github.com/WordPress/gutenberg/pull/36760.
  • I just noticed a few bugs stemming from the complexity, so I want to follow-up with a 2-in-1 PR: simplification and bugfixes.

Open Floor

Get involved in the latest call for testing

  • Alan Smodic asked for some insight or guidance on some issues that he and his team have flagged and added comments to. Wondering if these have ever been talked about before or how best we can help to potentially solve.
  • Publish datepicker time zone is server time instead of user time: #29306.
  • DateTimePicker Time Zone Selection: #31522.
  • Timepicker time resets when using AM/PM toggle: #29720.
  • @get_dave suggested getting @talldanwp to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. in the bi-weekly triage meetings.
  • @talldanwp suggested following up post 5.9.
  • @mciampini said he will flag it to the rest of the components folks,

Normalize Github labels to a single “[Type] Documentation” label

  • @mkaz informed us that there is a label in GitHub for “developer docs”, which is intended for issues specific to the developer documentation site.
  • He’s not sure the distinction is necessary and the additional label is confusing, as many docs are being labeled with one of the two labels.
  • Marcus proposed we remove the “developer docs” label and make sure any issues and PRs that have that label also have the “[Type] Documentation” label.
  • Folks in the meeting agreed with this proposal.

Call for input: can we run DB upgrade scripts as part of Gutenberg upgrade process?

  • @get_dave raised this Issue whereby meta tags were added to the post content on “Paste”.
  • The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issue has now been fixed but contributors are asking whether Gutenberg can add a one time operation on upgrade which runs a DB cleanup operation on all posts to remove this erroneous 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.).
  • I’d like to understand whether there is any prior art for achieving such a thing in Gutenberg – any input from @youknowriad or other Core folks would be appreciated.

Wrap up

Thanks to everyone who attended the meeting!

#core-editor, #core-editor-summary, #summary

A Week in Core – November 29, 2021

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 November 22 and November 29, 2021.

  • 42 commits
  • 60 contributors
  • 53 tickets created
  • 5 tickets reopened
  • 40 tickets closed

The Core team is currently working on the next major release, WordPress 5.9 🛠

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

Build/Test Tools

  • Configure Dependabot scanning for GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions – #54503
  • Correct the order and naming of expected and actual values in various tests – #53363
  • Fix warnings from stdClass::__invoke() callback mocks in 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/. tests – #53844
  • Remove unexpected output in wp_dashboard_recent_drafts() tests on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 – #53635, #53363
  • Rename classes in phpunit/tests/block-supports/ per the naming conventions – #53363
  • Rename classes in 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. template tests per the naming conventions – #53363
  • Replace assertEquals() with assertSame() in block template tests – #53364, #53363, #54335
  • Temporarily disable the check that the current recommended PHP version is actively supported – #54528
  • Use a simpler approach to test the output in some tests – #53635, #53363, #53363
  • Specify NodeJS version 14.x in the .nvmrc file – #54502

Bundled Themes

  • Twenty Twenty One: Remove Image block placeholder alignment override in editor styles – #54254
  • Twenty Twenty-One: Combine duplicate CSSCSS Cascading Style Sheets. rules – #53605
  • Twenty Twenty-One: Style adjustments for list-based widgets in the widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. editor – #53629
  • Twenty Twenty: Restore Editor post title styles after 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/ 11.4.0 updates – #54056

Docs

  • Add a @since note and description to wp_kses_attr() for new attribute-related KSES options: – #54261
  • Document the globals used in some Privacy 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. methods – #53399
  • Improve consistency of some DocBlocks in wp-admin/includes/post.php#53399
  • Miscellaneous DocBlockdocblock (phpdoc, xref, inline docs) corrections – #53399
  • Miscellaneous DocBlock corrections in wp-admin/includes/post.php#53399
  • Remove inaccurate part of the screen_settings 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. description – #54524
  • Various docblock corrections and improvements – #53399

Editor

  • Check the correct post type support property for initial_edits#53813
  • Ensure block style name does not contain spaces before creating the class – #54296
  • Remove Navigation Areas – #54506
  • Update wordpress packages: Update packages to include 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 from Gutenberg – #54487

External Libraries

  • Update getID3 to version 1.9.21 – #54162
  • Update the Requests library to version 2.0.0 – #54504
  • Upgrade PHPMailer to version 6.5.3 – #54514

Feeds

  • Remove reference to wp-atom.php in Atom feeds xml:base attribute – #47955

Media

  • Allow setting custom image alt text in custom 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. image – #46124
  • Ensure media preview is fully viewable in the “Add Media” modal – #53636
  • Fix TypeError and improve wp_exif_frac2dec() to only return int or float#54385
  • Replace tests/phpunit/data/images/sugar-mountain.jpg test image – #54385
  • Replace some array keys with their numeric equivalent – #53540

REST API

  • Ensure that the rest_after_insert_ action is executed in the templates controller. – #54520

Script Loader

  • Enqueue block stylesheet only when the corresponding block is used – #54457

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.

  • Check $term object before using it in get_term_feed_link()#50225
  • Use WP_Term object to retrieve the taxonomy in get_term_feed_link()#50225

Themes

  • Add block template resolution algorithm unit tests – #54478
  • Move the skip link to outside the canvas in block themes – #54491
  • Update the base folders for templates and template parts in block themes – #54493

Props

Thanks to the 60 people who contributed to WordPress Core on Trac last week: @jrf (6), @audrasjb (4), @sabernhardt (4), @costdev (4), @mukesh27 (4), @SergeyBiryukov (3), @spacedmonkey (2), @bernhard-reiter (2), @adamsilverstein (2), @peterwilsoncc (2), @zieladam (2), @Boniu91 (2), @justinahinon (1), @multidots1896 (1), @wojsmol (1), @jorgefilipecosta (1), @chintan1896 (1), @schlessera (1), @Synchro (1), @datagutten (1), @noisysocks (1), @dd32 (1), @dustinrue (1), @soulseekah (1), @szepeviktor (1), @youknowriad (1), @ryelle (1), @Shaharyar10 (1), @shital-patel (1), @poena (1), @circlecube (1), @Rahmohn (1), @sourovroy (1), @hugod (1), @webmandesign (1), @joedolson (1), @Ankit K Gupta (1), @get_dave (1), @shireling (1), @mai21 (1), @hilayt24 (1), @desrosj (1), @praem90 (1), @stevegs (1), @tobiasbg (1), @tw2113 (1), @siliconforks (1), @shimotomoki (1), @nrqsnchz (1), @devutpol (1), @amustaque97 (1), @hellofromtonya (1), @pbiron (1), @afragen (1), @dlh (1), @Starbuck (1), @afercia (1), @anevins (1), @mikeschroder (1), and @talldanwp (1).

Congrats and welcome to our 10 new contributors of the week: @multidots1896, @wojsmol, @datagutten, @dustinrue, @Shaharyar10, @hugod, @praem90, @stevegs, @shimotomoki, and @amustaque97 ♥️

Core committers: @sergeybiryukov (14), @audrasjb (13), @hellofromtonya (3), @johnbillion (3), @spacedmonkey (2), @youknowriad (2), @noisysocks (2), @desrosj (2), and @peterwilsoncc (1).

#5-9, #core, #week-in-core

What’s new in Gutenberg 12.0 ( 24 November)

These “What’s new in 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/…” 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 an update every time a Gutenberg release is done (every 2 weeks more or less) and they explain the features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project.


It’s the end of November and Gutenberg 12.0.0 has been released! With contributor efforts being geared towards preparing for WordPress 5.9, this release is more maintenance-focused but still offers a few new features as well as many 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.

Table of Contents

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. Styles Preview

Until this release, Block Styles appeared in both the block’s toolbar and in the editor’s 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.. These previews, although rather small, added to the overall height of the sidebar accordion. Gutenberg 12.0 moves the sidebar previews so they only appear when the style is hovered or has keyboard focus. This reduces the overall sidebar footprint and also puts more emphasis on the style’s name.

Before this release, the Featured Image block did not provide a clear representation during its placeholder state, displaying a selection box with a fixed height. With Gutenberg 12.0 the block’s placeholder state is a better representation of how it would look when using real images, as it displays a placeholder image that respects both the height and width settings.

Paragraph block combined typography controls

As of 12.0.0, the Drop Cap setting for the paragraph block has been moved from its own section in the Block Settings sidebar into the Typography section. This change keeps all Typography related controls together for the block to provide a consistent experience.

Site Editor Welcome Guide

In preparation to stabilize and release the block theme Editor in WordPress 5.9, a new welcome guide has been added to help users get started with both the Editor and the Styles sidebar.

Site editor welcome guide modal.

Official 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. Schema updates

Official schemas for block.json and theme.json were introduced with Gutenberg 11.9.0. This release provides some updates as well as new URLs to easily access them:

The URLs above redirect to the latest version of the schema but as WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. versioned are released, they can also target specific versions of WordPress starting with WordPress 5.9!

Theme.json example.

New Developer Experience section in the Changelog

Recently, contributors have been putting an even bigger focus on improving the developer experience, and there is more to come. So much so, that we are introducing a new section for it in the changelog. This speaks to the commitment from contributors to not only create a great experience for users of Gutenberg but also those that extend it. To keep updated or contribute to the discussion, you can check the recent GitHub discussions on Developer Experience.

Changelog

Enhancements

Block Library

  • Move WP_REST_Block_Navigation_Areas_Controller from Gutenberg to Core. (36374)
  • Change all the uses of “website” to “site”. (36220)
  • Featured Image: Let Featured Image block inherit dimensions, look like a placeholder. (36517)
  • Navigation: Enable Previews for Navigation Link Blocks. (36412)
  • Navigation: Apply 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. functions to Nav block menu drops when selecting existing Menu. (36301)
  • Navigation: Refactor and simplify setup state. (36375)
  • Navigation: Rename fse_navigation_area to wp_navigation_area. (36460)
  • Navigation: Return wp error from wp_insert_post. (36483)
  • Paragraph: Merge text settings into typography panel. (36334)
  • Remove textdomain from calendar block. (36500)

Site Editor

  • Add welcome guide. (36172)
  • Update back button URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. (36313)
  • Improve compatibility with menu endpoints WordPress 5.9. (36372)
  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. to any errors coming up in gutenberg_migrate_menu_to_navigation_post. (36461)
  • Change edit links for templates and template parts. (36294)
  • Update site editor title truncation. (36436)
  • Add template_type guards. (36318)

Block 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.

  • Update schema to require either a type or an enum. (36267)
  • Add _wp_array_set and _wp_to_kebab_case to 5.8 compat. (36399)

Design Tools

  • Letter spacing: Update label copy. (36385)

Style

  • Add block icon next to blocks list. (36520)
  • theme.json: Adds a setting property that enables some other ones. (36246).
    • This was incorrectly added to the 12.0.0 milestone.
  • Block Styles: Show style preview when hovered or focused. (34522)

Icons

  • Add the missing comment edit link icon. (36565)
  • Remove hard coded color from query pagination icons. (35837)
  • Remove hard-coded values on icons. (36564)

Components

  • ToolsPanel: Allow additional props on ToolsPanel. (36428)
  • Typography Panel: Make letter spacing jsDoc and prop use consistent. (36367)

Bug Fixes

Block Library

  • Fix background colours in nested submenus. (36476)
  • Fix colour rendering in Navigation overlay. (36479)
  • Fix duplicate custom classnames in navigation submenu block. (36478)
  • Fix submenu justification and spacer orientation. (36340)
  • Group – Fix overzealous regex when restoring inner containers. (36221)
  • Hide visilibility and status for navigation posts. (36363)
  • Nav block menu switcher – decode HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. entities and utilise accessible markup pattern. (36397)
  • Navigation: Fix click-button size, submenu directions, scrollbars. (36215)
  • Page List block: Fix space before href attribute. (36505)
  • Page List: Use core entities instead of direct apiFetch. (36531)
  • Post Comments Form: Ensure typography styles are applied to child elements. (36425)
  • Post title block default CSSCSS Cascading Style Sheets.: Add a break-word rule by default. (35703)

Block API

  • Use firstChild and lastChild when parsing lists from MS Word. (36019)

Full Site Editing

  • Add the ability to opt-out of Core color palette V2. (36492)
  • Fix layout shift in core/post-featured-image block with isLink enabled. (36552)
  • Template Part Block: Add some guards. (36324)
  • Chore: Add rewrite false to global styles CPT. (36273)
  • Revert “theme.json: Adds a setting property that enables some other ones”. (36477)
  • Update more references to __experimental menu endpoints to make them stable. (36386)

Site Editor

  • Fix site editor reset styles in WP 5.9. (36390)
  • Site Editor – prevent loading state from showing the adminadmin (and super admin) menu. (36455)

Global Styles

  • Replace get_theme_file_path in theme_has_support. (36398)
  • Chore: Fix small typos on the rest endpoints. (36272)

Block Editor

  • Strip 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. tags from pasted links in Chromium. (36356)
  • Add webp extension in filePasteHandler and getPasteEventData. (36361)
  • Fix mobile horizontal scrollbar. (36567)
  • Polish metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. container. (36297)

CSS & Styling

  • Update theme styles for the code block. (36282)

Documentation

Handbook

  • “npm install” suggestion provides a better learning experience. (36217)
  • Added specific links to agenda and notes posts related to core editor meetings. (36199)
  • Schemastore – $schema is VS Code-specific. (36179)
  • Update GIF image in documentation with wp.org schema URL. (36456)
  • Update Versions in WordPress to include 5.9. (36156)
  • Update theme.json schema to refer to wp.org URL. (36332)

Components Package

  • Update combobox-control component readme. (36413)
  • Update wordpress/components changelog. (36448)

Developer Experience

  • Add block.json schema definition to core blocks. (35900)
  • Add pattern to name key in block.json Schema. (36343)
  • Update schema URL to wp.org domain. (36316)
  • Allow block.json attribute type to be an array. (36295)
  • Fix schema to allow for custom blocks in theme.json. (36341)

Code Quality

  • Change @Package to WordPress in block-library. (36494)
  • postcss-themes: Fix PostCSS 8 deprecation warning. (36284)
  • Data: Clean up registerGenericStore param names. (36300)
  • Prepare navigation php code for core 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.. (36336)
  • Add comment to Remove 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. to allow WP variables after min version is 5.8. (36281)
  • Update: Centralize safe_style_css usages. (36280)
  • DEWP: Fix deprecation warning. (36285)

Tools

Testing

  • E2E: Add more Cover block tests. (36321)
  • Fix Performance CI tests and make them always use the latest major as base 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".. (36463)
  • Fix failing tests and compatibility with 5.9. (36368)
  • Add integration tests with core blocks schema validation. (36351)
  • Skip flaky image block test. (36446)
  • Theme switch on the global styles 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/. 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.. (36277)

Build Tooling

  • Add TypeScript for builds and tests. (36260)
  • stylelint-config: Widen the acceptable version range for the ‘stylelint’ peerDependency. (36518)
  • Update Babel packages to 7.16 version. (36244)

Fix not transforming logical assignments for packages. (36484)

Performance  Benchmark

VersionTime to Render First BlockKeyPress Event (typing)
Gutenberg 12.06.18s39.99ms
Gutenberg 11.95.89s40.75ms
WordPress 5.86.56s49.54ms

Thank you to @shaunandrews for the assets included in this post, @priethor for coordinating the release process and proofreading, @vcanales for the moral support and answering questions about the release process, and to all those who contributed to this release!

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

Performance Chat Agenda: November 30, 2021

Here is the agenda for this week’s performance team meeting to occur on November 30, 2021, at 16:00 UTC.

This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

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

CSS Chat Summary: 18 November 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Announcements & housekeeping

  • The next meeting will be on Thursday 25 November at 17:00 UTC. Please add your name to the Meeting Facilitator schedule document if you would like to contribute by facilitating this or any future meetings
  • @notlaura suggested breaking for holidays after December 16th and starting up again January 6th 2022
  • @khoipro pointed out that the new meeting time is midnight in APAC which led to a short discussion about meeting times. The conclusion was that we can revisit the meeting time again in the future

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

Thanks everybody!

#core-css, #summary

Dev Chat Summary for November 24, 2021

@hellofromTonya led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <devchat> in #core on 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/..

Notable News and blogblog (versus network, site) posts

Team Reps

  • @marybaum will be a new Core Team Rep for 2022.
  • Thanks to @francina for serving in this role!
  • @audrasjb will continue in this role until another 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. is found.

Interested in being a Core Team Rep? Reach out to @audrasjb.

WordPress 5.9

  • @jeffpaul asked if there are any 5.9 blockers that are in specific need of help and asked what type of help they need (engineering, design, testing, etc).
  • @hellofromTonya posted an update on 5.9 blockers and scheduling. Design help is needed for Global styles & Design tools.
  • There is an open Call for Testing for Safari.
  • Everyone is invited to help wherever possible.
  • The release squad is keeping a daily close eye on progress, needs, and any blockers that might surface. Discussions and updates are centralized in the #5-9-release-leads channel on Slack.

Component Team Updates

Build/Test Tools

@sergeybiryukov gave an update:

  • Dependabot scanning is now configured for GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions. This eliminates the need to manually check all GitHub Actions used within workflow files for updates. See ticketticket Created for both bug reports and feature development on the bug tracker. #54503 for more details.
  • NodeJS is pinned to the 14.x version in the .nvmrc file to ensure contributors are able to contribute without issue until compatibility with version 16.x can be confirmed in both 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. and the 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/ repository on GitHub. See ticket #54502 for more details.
  • Some PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warnings from stdClass::__invoke() callback mocks were fixed in 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/. tests. See ticket #53844 for more details.
  • The timeout for GitHub Actions jobs was lowered so runaway or stalled processes don’t risk running for the default timeout duration of six hours. See ticket #53363 for more details.

@sergeybiryukov shared: No major news this week

Open Floor

  • @afragen asked for feedback on the Plugin Dependencies project for WordPress 6.0. Reach out to @peterwilsoncc if you wish to have editing access.
  • @jeffpaul asked how we are progressing on the Pre Beta 1 tasks and asked if there are any items that need help.
  • @hellofromTonya replied that there are some 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 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. that need to be compiled and published.
  • @audrasjb has been marking tickets that need Dev notes.
  • @mkaz noted that documentation for WordPress 5.9 could use some help and posted a link to the requirements. Contributors are invited to reach out to @mkaz with any questions.
  • @jeffpaul is working on the WordPress 5.9 HelpHub page.
  • @abhanonstopnewsuk noted that the latest checks for the About and Help page were carried out on Monday November 22, 2021. The next check is on Monday November 29, 2021 at 20:30 UTC.
  • @audrasjb will be leading 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. scrub on November 25, 2021 at 21:00 UTC. See the 5.9 Bug Scrub schedule.
  • With Thanksgiving taking place in the US on November 25, 2021, @hellofromTonya thanked the community for all contributions.

Props to @costdev for writing the devchat summary.

#5-9, #dev-chat, #summary