Title: 2021 – Page 7 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
5:47 pm _on_ November 17, 2021     
Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/),
[agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core ( 743 )](https://make.wordpress.org/core/tag/core/),
[dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/)   

# 󠀁[Dev Chat Agenda for November 17, 2021](https://make.wordpress.org/core/2021/11/17/dev-chat-agenda-for-november-17-2021/)󠁿

Here is the agenda for this week’s developer meeting to occur on [November 17, 2021, at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211117T2000).

**Please note that depending on your timezone, the time may have changed with the
end of daylight saving time.**

## Blogblog (versus network, site) Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/
or volunteers:

 * [WordPress 5.9 Beta 1 will be delayed for 24 hours](https://make.wordpress.org/core/2021/11/16/wordpress-5-9-beta-1-will-be-delayed-for-24-hours/)
 * [A Week in Core – November 15, 2021](https://make.wordpress.org/core/2021/11/16/a-week-in-core-november-15-2021/)
 * [What’s new in Gutenberg 11.9.0 (10 November)](https://make.wordpress.org/core/2021/11/12/whats-new-in-gutenberg-11-9-0-10-november/)

Have you been working on 5.9 related issues? Let everyone know!

## Components check-in and status updates

 * Check-in with each component for status updates.
 * Poll for components that need assistance.

## Open Floor

Do you have something to propose for the agenda, or a specific item relevant to 
the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group
can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW)
channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/).

[#5-9](https://make.wordpress.org/core/tag/5-9/), [#agenda](https://make.wordpress.org/core/tag/agenda/),
[#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
11:09 pm _on_ November 16, 2021     
Tags: [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/),
[5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core ( 743 )](https://make.wordpress.org/core/tag/core/),
[week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)   

# 󠀁[A Week in Core – November 15, 2021](https://make.wordpress.org/core/2021/11/16/a-week-in-core-november-15-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 8 and
November 15, 2021.

 * 116 commits (!)
 * 204 contributors (!)
 * 57 tickets created
 * 10 tickets reopened
 * 89 tickets closed

The Core team is currently working on the 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., 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](https://core.trac.wordpress.org/timeline?from=11%2F15%2F2021&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update).
The following is a summary of commits, organized by component and/or focus.

## Code changes

### About/Help

 * Add commas to end of multi-line array items – [#54357](https://core.trac.wordpress.org/ticket/54357)
 * add docs links to several screens – [#54357](https://core.trac.wordpress.org/ticket/54357)

### Administration

 * Restores “Customize” menu item for non-blockBlock Block is the abstract term 
   used to describe units of markup that, composed together, form the content or
   layout of a webpage using the WordPress editor. The idea combines concepts of
   what in the past may have achieved with shortcodes, custom HTML, and embed discovery
   into a single consistent API and user experience. themes and moves for block 
   themes – [#54418](https://core.trac.wordpress.org/ticket/54418)

### Bootstrap/Load

 * Add `HTTP/3` as a valid HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol.
   HTTP is the underlying protocol used by the World Wide Web and this protocol 
   defines how messages are formatted and transmitted, and what actions Web servers
   and browsers should take in response to various commands. protocol. – [#54404](https://core.trac.wordpress.org/ticket/54404)
 * Bootstrap/Load: Check `$_SERVER['SCRIPT_NAME']` exists before passing to `strpos()`
   in `wp_fix_server_vars()` – [#54142](https://core.trac.wordpress.org/ticket/54142)

### Build/Test Tools

 * Cache the results of `PHP_CodeSniffer` across workflow runs – [#49783](https://core.trac.wordpress.org/ticket/49783)
 * Exclude plugins and non-bundled themes from PHPPHP The web scripting language
   in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher
   compatibility scans – [#54425](https://core.trac.wordpress.org/ticket/54425)
 * Make adjustments to how Quick Draft tests confirm expected behavior – [#54409](https://core.trac.wordpress.org/ticket/54409)
 * Mock no results remote request in WP_REST_Block_Directory_Controller:: get_items()–
   [#54420](https://core.trac.wordpress.org/ticket/54420)
 * Mock remote request for `WP_REST_Block_Directory_Controller::get_items()` – [#54420](https://core.trac.wordpress.org/ticket/54420)
 * Mock remote request for unknown pluginPlugin A plugin is a piece of software 
   containing a group of functions that can be added to a WordPress website. They
   can extend functionality or add new features to your WordPress websites. WordPress
   plugins are written in the PHP programming language and integrate seamlessly 
   with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. in `WP_REST_Plugins_Controller::
   create_item()` – [#54420](https://core.trac.wordpress.org/ticket/54420)
 * Restore the httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure.
   HTTPS is the secure version of HTTP, the protocol over which data is sent between
   your browser and the website that you are connected to. The 'S' at the end of
   HTTPS stands for 'Secure'. It means all communications between your browser and
   the website are encrypted. This is especially helpful for protecting sensitive
   data like banking information. URLURL A specific web address of a website or 
   web page on the Internet, such as a website’s URL www.wordpress.org for browserify-
   aes – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Update all 3rd party GitHubGitHub GitHub is a website that offers online implementation
   of git repositories that can easily be shared, copied and modified by other developers.
   Public repositories are free to host, private repositories require a paid subscription.
   GitHub introduced the concept of the ‘pull request’ where code changes done in
   branches by contributors can be reviewed and discussed before being merged by
   the repository owner. [https://github.com/](https://github.com/) actions to the
   latest versions – [#53363](https://core.trac.wordpress.org/ticket/53363)
 * Change default GitHub 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". to 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.–
   [#54399](https://core.trac.wordpress.org/ticket/54399)
 * Update qUnit test fixtures after [[52128]](https://core.trac.wordpress.org/changeset/52128)–
   [#54336](https://core.trac.wordpress.org/ticket/54336)

### Bundled Theme

 * Display required text field in core themes – [#54392](https://core.trac.wordpress.org/ticket/54392)
 * Import Twenty Twenty-Two, the new default theme for WordPress 5.9 – [#54318](https://core.trac.wordpress.org/ticket/54318)
 * Twenty Eleven: Improve comment form styling for required fields – [#54408](https://core.trac.wordpress.org/ticket/54408)
 * Twenty Nineteen: Apply coding standards fix from running `composer format` – 
   [#54392](https://core.trac.wordpress.org/ticket/54392)
 * Twenty Twenty-One: Add privacy policy link to footer – [#53445](https://core.trac.wordpress.org/ticket/53445)
 * Twenty Twenty-One: Correct default image alignment in the editor – [#53809](https://core.trac.wordpress.org/ticket/53809)
 * Twenty Twenty-One: Prevent printing skip link focus fix when `SCRIPT_DEBUG` is
   enabled – [#54429](https://core.trac.wordpress.org/ticket/54429)
 * Twenty Twenty-Two: Import the `assets` directory from GitHub – [#52081](https://core.trac.wordpress.org/ticket/52081)
 * Twenty Twenty-Two: Import the latest changes from GitHub – [#54318](https://core.trac.wordpress.org/ticket/54318)

### Coding Standards

 * Minor alignment fix after [[52058]](https://core.trac.wordpress.org/changeset/52058)–
   [#52058](https://core.trac.wordpress.org/ticket/52058)
 * PHP Code style errors – [#43700](https://core.trac.wordpress.org/ticket/43700)
 * PHP Code style errors – [#43700](https://core.trac.wordpress.org/ticket/43700)
 * Rename the `$gzData` argument to `$gz_data` in `WP_Http_Encoding::compatible_gzinflate()`–
   [#53359](https://core.trac.wordpress.org/ticket/53359)
 * Revert accidental image changes in [[52171]](https://core.trac.wordpress.org/changeset/52171)–
   [#54168](https://core.trac.wordpress.org/ticket/54168)
 * Revert unrelated change to `wp_send_user_request()` – [#43700](https://core.trac.wordpress.org/ticket/43700)
 * Use strict comparison in `wp-admin/includes/ms.php` – [#47422](https://core.trac.wordpress.org/ticket/47422)

### Comments

 * Don’t output “cancel comment reply link” if comments aren’t threaded – [#37267](https://core.trac.wordpress.org/ticket/37267)
 * Use `get_comment_author()` to retrieve the comment author name in `get_comment_reply_link()`–
   [#53678](https://core.trac.wordpress.org/ticket/53678)

### Database

 * WPDB: Capture error in `wpdb::$last_error` when insert fails instead of silently
   failing for 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. data or value too
   long – [#37267](https://core.trac.wordpress.org/ticket/37267)

### Docs

 * Add missing documentation for the `$javascript` parameter of the `wp_inline_script_attributes`
   filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Avoid using “CPT” instead of “custom post typeCustom Post Type WordPress can 
   hold and display many different types of content. A single item of such a content
   is generally called a post, although post is also a specific post type. Custom
   Post Types gives your site the ability to have templated posts, to simplify the
   concept.” – [#53399](https://core.trac.wordpress.org/ticket/53399), [#54335](https://core.trac.wordpress.org/ticket/54335),
   [#54336](https://core.trac.wordpress.org/ticket/54336)
 * List the expected return type first in a few functions – [#53399](https://core.trac.wordpress.org/ticket/53399)

### Editor

 * Update SVNSVN Subversion, the popular version control system (VCS) by the Apache
   project, used by WordPress to manage changes to its codebase. props to ignore
   new asset files – [#54337](https://core.trac.wordpress.org/ticket/54337), [#53361](https://core.trac.wordpress.org/ticket/53361)
 * Update SVN props to ignore new asset files – [#54337](https://core.trac.wordpress.org/ticket/54337),
   [#53361](https://core.trac.wordpress.org/ticket/53361)
 * Add documentation for the `$block_editor_context` parameter of the `block_editor_rest_api_preload_paths`
   hook – [#52920](https://core.trac.wordpress.org/ticket/52920), [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Site Editor and PHP changes 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/](https://wordpress.org/gutenberg/)
   10.1 – 11.9 – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Site Editor: Load as full screen by default – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Add Navigation Area infrastructure – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Add block theme infrastructure – [#54335](https://core.trac.wordpress.org/ticket/54335)
 * Add get_query_pagination_arrow function to core
 * Add public functions for interacting with global styles & settings – [#54336](https://core.trac.wordpress.org/ticket/54336)
 * Fix fatal call to add_query_args() – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Fix how the Site Editor is linked to – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Fix incorrect access of ID field – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Global Styles Rest endpoints – [#54336](https://core.trac.wordpress.org/ticket/54336)
 * Global styles user content escaping – [#54336](https://core.trac.wordpress.org/ticket/54336)
 * Load iframed assets in Site Editor – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Update wordpress packages – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Fix Linting error affecting trunk
 * Update wordpress packages – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Update wordpress packages – [#54337](https://core.trac.wordpress.org/ticket/54337)
 * Update block-theme-pl_PL.mo file. – [#54336](https://core.trac.wordpress.org/ticket/54336)

### Embeds

 * Conditionally enqueue `wp-embed` only if needed and send `ready` message in case
   script loads after post embed windows – [#44632](https://core.trac.wordpress.org/ticket/44632),
   [#44306](https://core.trac.wordpress.org/ticket/44306)
 * Fix inclusion of `wp-embed-template` script and style when `SCRIPT_DEBUG` is 
   disabled – [#44632](https://core.trac.wordpress.org/ticket/44632)
 * Fix parsing of post embeds in `wp_filter_oembed_result()` by appending `wp-embed`
   script instead of prepending it in `get_post_embed_html()` – [#44632](https://core.trac.wordpress.org/ticket/44632)

### External Libraries

 * Update the `regenerator-runtime` package to version `0.13.9` – [#54027](https://core.trac.wordpress.org/ticket/54027)
 * Update ‘reactReact React is a JavaScript library that makes it easy to reason
   about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/)’
   and ‘react-dom’ – [#54337](https://core.trac.wordpress.org/ticket/54337)

### General

 * Add “noopener” to `wp_list_bookmarks()` output – [#53839](https://core.trac.wordpress.org/ticket/53839)
 * General: Convert `wp_list_filter()` into a wrapper for `wp_filter_object_list()`–
   [#53988](https://core.trac.wordpress.org/ticket/53988)
 * General: Minor fixes to Global Style related code – [#54336](https://core.trac.wordpress.org/ticket/54336)

### HTTP 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.

 * Ensure value returned from `'http_allowed_safe_ports'` is an array to avoid PHP
   8+ TypeError fatal error – [#54331](https://core.trac.wordpress.org/ticket/54331)
 * Introduce `'http_allowed_safe_ports'` filter in `wp_http_validate_url()` – [#54331](https://core.trac.wordpress.org/ticket/54331)

### Internationalization

 * Add language switcher on login/registration screens – [#43700](https://core.trac.wordpress.org/ticket/43700)
 * Add missing translationtranslation The process (or result) of changing text, 
   words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/2021/page/7/?output_format=md#l10n),
   [internationalization](https://make.wordpress.org/core/2021/page/7/?output_format=md#i18n).
   wrapper for the Global Styles post type description – [#54336](https://core.trac.wordpress.org/ticket/54336)

### Login and Registration

 * Fix failing test for “email already exists” registration error improvement – 
   [#53631](https://core.trac.wordpress.org/ticket/53631)
 * Improve “email already exists” registration error message – [#53631](https://core.trac.wordpress.org/ticket/53631)
 * Improve messaging for invalid log-out nonces – [#52600](https://core.trac.wordpress.org/ticket/52600)
 * Pass `$errors` parameter to `registration_redirect` filter – [#53992](https://core.trac.wordpress.org/ticket/53992)
 * Wrap long usernames in login error message – [#37617](https://core.trac.wordpress.org/ticket/37617)

### Mail

 * Add `wp_mail_succeeded` hook to `wp_mail` – [#53826](https://core.trac.wordpress.org/ticket/53826)

### Media

 * Add “webp” extension to wp.media.controller.Library `isImageAttachment` – [#53917](https://core.trac.wordpress.org/ticket/53917)
 * Change upload button to a file input for better e2e targeting – [#54168](https://core.trac.wordpress.org/ticket/54168)
 * 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. modal loads only selected image – [#42937](https://core.trac.wordpress.org/ticket/42937)
 * Featured image modal loads only selected image – [#53765](https://core.trac.wordpress.org/ticket/53765)
 * Refine the heuristics to exclude certain images and iframes from being lazy-loaded
   to improve performance – [#53675](https://core.trac.wordpress.org/ticket/53675),
   [#50425](https://core.trac.wordpress.org/ticket/50425)
 * Revert media uploader input change in [[52059]](https://core.trac.wordpress.org/changeset/52059)–
   [#54168](https://core.trac.wordpress.org/ticket/54168), [#54411](https://core.trac.wordpress.org/ticket/54411)

### Menus

 * Add audible notice on menu item add or remove – [#53840](https://core.trac.wordpress.org/ticket/53840)

### Options, MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. APIs

 * Correct docs for `$_meta_value` parameter in `xxx_{$meta_type}_meta` 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. – [#53102](https://core.trac.wordpress.org/ticket/53102)

### Posts, Post Types

 * Add `$old_status` parameter to `{$new_status}_{$post->post_type}` action – [#36180](https://core.trac.wordpress.org/ticket/36180)
 * Mark the `wp_global_styles` post type as `_builtin` – [#54336](https://core.trac.wordpress.org/ticket/54336)
 * Remove `gutenberg` text domain from post type strings – [#54336](https://core.trac.wordpress.org/ticket/54336),#
   54337
 * Update `_edit_last` meta when posts are edited in bulk – [#42446](https://core.trac.wordpress.org/ticket/42446)

### Quick/Bulk Edit

 * Disable auto-correct for slugs – [#50499](https://core.trac.wordpress.org/ticket/50499)

### REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) 󠀁[https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)󠁿

 * Add /wp/v2/block-navigation-areas endpoint – [#54393](https://core.trac.wordpress.org/ticket/54393)
 * Add batch support for posts and terms controllers – [#53063](https://core.trac.wordpress.org/ticket/53063)
 * Expose the site icon in the REST API index – [#52321](https://core.trac.wordpress.org/ticket/52321)
 * Introduce Menu management endpoints – [#40878](https://core.trac.wordpress.org/ticket/40878)
 * Regenerate wp-api-generated.js after [[52068]](https://core.trac.wordpress.org/changeset/52068)–
   [#53063](https://core.trac.wordpress.org/ticket/53063)
 * Remove experimental block menu item types – [#40878](https://core.trac.wordpress.org/ticket/40878)

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

 * Introduce `wp_get_post_revisions_url()` to get URL for editing revisions – [#39062](https://core.trac.wordpress.org/ticket/39062)

### 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](https://codex.wordpress.org/Taxonomies#Default_Taxonomies)󠁿.

 * Allow `get_*_*_link()` and `edit_term_link()` functions to accept a term ID, `
   WP_Term`, or term object – [#50225](https://core.trac.wordpress.org/ticket/50225)
 * Change some static strings to registration labels – [#43060](https://core.trac.wordpress.org/ticket/43060)
 * Clarify the taxonomy labels for customizing the field descriptions on Edit Tags
   screen: – [#43060](https://core.trac.wordpress.org/ticket/43060)
 * Display update notices when adding terms – [#42937](https://core.trac.wordpress.org/ticket/42937)
 * Document that the `get_terms` filter can have `null` for `$taxonomies` – [#54222](https://core.trac.wordpress.org/ticket/54222)

### Template

 * Fix “undefined index: 00” when archive month query is empty in `wp_title()` –
   [#31521](https://core.trac.wordpress.org/ticket/31521)

### Themes

 * Avoid fatal error loading adminadmin (and super admin) styles when `SCRIPT_DEBUG`
   is `false` – [#54401](https://core.trac.wordpress.org/ticket/54401), [#54336](https://core.trac.wordpress.org/ticket/54336)
 * Check both parent and child themes for a `theme.json` file – [#54401](https://core.trac.wordpress.org/ticket/54401)
 * Force a scrollbar on the Themes page to prevent visual shake on hover – [#53478](https://core.trac.wordpress.org/ticket/53478)
 * Twenty Twenty-Two is now the default theme – [#54318](https://core.trac.wordpress.org/ticket/54318)
 * Update 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. classes for WordPress 5.9–
   [#54336](https://core.trac.wordpress.org/ticket/54336)
 * Hide Customize from admin bar when using a block theme – [#54337](https://core.trac.wordpress.org/ticket/54337)

### Upgrade/Install

 * Deactivate the Gutenberg plugin if its version is 11.8 or lower – [#54405](https://core.trac.wordpress.org/ticket/54405)
 * Update screen reader text counts in adminbar – [#29022](https://core.trac.wordpress.org/ticket/29022)

### Users

 * Introduce `wp_list_users()` function – [#15145](https://core.trac.wordpress.org/ticket/15145)
 * Prevent infinite loopLoop The Loop is PHP code used by WordPress to display posts.
   Using The Loop, WordPress processes each post to be displayed on the current 
   page, and formats it according to how it matches specified criteria within The
   Loop tags. Any HTML or PHP code in the Loop will be processed on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop)
   when using capabilitycapability A **capability** is permission to perform one
   or more types of task. Checking if a user has a capability is performed by the`
   current_user_can` function. Each user of a WordPress site might have some permissions
   but not others, depending on their role. For example, users who have the Author
   role usually have permission to edit their own posts (the “edit_posts” capability),
   but not permission to edit other users’ posts (the “edit_others_posts” capability).
   checks during `determine_current_user` on multisitemultisite Used to describe
   a WordPress installation with a network of multiple blogs, grouped by sites. 
   This installation type has shared users tables, and creates separate database
   tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**,**
   site** – [#53386](https://core.trac.wordpress.org/ticket/53386)

### Widgets

 * Use `isset()` in `WP_Widget:: display_callback()` to support `ArrayIterator` 
   and `ArrayObject` – [#52728](https://core.trac.wordpress.org/ticket/52728)
 * Wraps long 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. titles in classic Widgets screen – [#37451](https://core.trac.wordpress.org/ticket/37451)

## Props

_Please note that it was the most prolific week since we restarted the Week in Core
blogblog (versus network, site) posts last year!_

**Thanks to the 204 (!) people who contributed to WordPress Core on Trac last week:**
[@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (28), [@audrasjb](https://profiles.wordpress.org/audrasjb/)(
21), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) (14), [@desrosj](https://profiles.wordpress.org/desrosj/)(
11), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) (11), [@costdev](https://profiles.wordpress.org/costdev/)(
10), [@johnbillion](https://profiles.wordpress.org/johnbillion/) (9), [@oandregal](https://profiles.wordpress.org/oandregal/)(
8), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) (7), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)(
7), [@poena](https://profiles.wordpress.org/poena/) (6), [@swissspidy](https://profiles.wordpress.org/swissspidy/)(
6), [@afercia](https://profiles.wordpress.org/afercia/) (6), [@youknowriad](https://profiles.wordpress.org/youknowriad/)(
6), [@noisysocks](https://profiles.wordpress.org/noisysocks/) (5), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/)(
5), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (4), [@birgire](https://profiles.wordpress.org/birgire/)(
4), [@TimothyBlynJacobs](https://profiles.wordpress.org/timothyblynjacobs/) (4),
[@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (4), [@mukesh27](https://profiles.wordpress.org/mukesh27/)(
3), [@Mamaduka](https://profiles.wordpress.org/mamaduka/) (3), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)(
3), [@antonvlasenko](https://profiles.wordpress.org/antonvlasenko/) (3), [@aristath](https://profiles.wordpress.org/aristath/)(
3), [@pento](https://profiles.wordpress.org/pento/) (3), [@dd32](https://profiles.wordpress.org/dd32/)(
3), [@chaion07](https://profiles.wordpress.org/chaion07/) (3), [@westonruter](https://profiles.wordpress.org/westonruter/)(
3), [@jorbin](https://profiles.wordpress.org/jorbin/) (3), [@TobiasBg](https://profiles.wordpress.org/tobiasbg/)(
2), [@chrisvanpatten](https://profiles.wordpress.org/chrisvanpatten/) (2), [@joedolson](https://profiles.wordpress.org/joedolson/)(
2), [@soean](https://profiles.wordpress.org/soean/) (2), [@dilipbheda](https://profiles.wordpress.org/dilipbheda/)(
2), [@manishamakhija](https://profiles.wordpress.org/manishamakhija/) (2), [@kjellr](https://profiles.wordpress.org/kjellr/)(
2), [@garrett-eclipse](https://profiles.wordpress.org/garrett-eclipse/) (2), [@flixos90](https://profiles.wordpress.org/flixos90/)(
2), [@kafleg](https://profiles.wordpress.org/kafleg/) (2), [@Clorith](https://profiles.wordpress.org/clorith/)(
2), [@dlh](https://profiles.wordpress.org/dlh/) (2), [@Boniu91](https://profiles.wordpress.org/boniu91/)(
2), [@justinahinon](https://profiles.wordpress.org/justinahinon/) (2), [@ryelle](https://profiles.wordpress.org/ryelle/)(
2), [@ocean90](https://profiles.wordpress.org/ocean90/) (2), [@mte90](https://profiles.wordpress.org/mte90/)(
2), [@hareesh-pillai](https://profiles.wordpress.org/hareesh-pillai/) (2), [@jrf](https://profiles.wordpress.org/jrf/)(
2), [@webcommsat](https://profiles.wordpress.org/webcommsat/) (2), [@drewapicture](https://profiles.wordpress.org/drewapicture/)(
2), [@tobifjellner](https://profiles.wordpress.org/tobifjellner/) (2), [@bgardner](https://profiles.wordpress.org/bgardner/)(
1), [@rviscomi](https://profiles.wordpress.org/rviscomi/) (1), [@sourav926](https://profiles.wordpress.org/sourav926/)(
1), [@jonoaldersonwp](https://profiles.wordpress.org/jonoaldersonwp/) (1), [@azaozz](https://profiles.wordpress.org/azaozz/)(
1), @briceduclos (1), [@colorful-tones](https://profiles.wordpress.org/colorful-tones/)(
1), [@tweetythierry](https://profiles.wordpress.org/tweetythierry/) (1), [@pbearne](https://profiles.wordpress.org/pbearne/)(
1), [@sebastianpisula](https://profiles.wordpress.org/sebastianpisula/) (1), [@aaroncampbell](https://profiles.wordpress.org/aaroncampbell/)(
1), [@kapilpaul](https://profiles.wordpress.org/kapilpaul/) (1), [@xknown](https://profiles.wordpress.org/xknown/)(
1), [@chriscct7](https://profiles.wordpress.org/chriscct7/) (1), [@donmhico](https://profiles.wordpress.org/donmhico/)(
1), [@gziolo](https://profiles.wordpress.org/gziolo/) (1), [@malthert](https://profiles.wordpress.org/malthert/)(
1), [@greenshady](https://profiles.wordpress.org/greenshady/) (1), [@nacin](https://profiles.wordpress.org/nacin/)(
1), [@rohan013](https://profiles.wordpress.org/rohan013/) (1), [@bernhard-reiter](https://profiles.wordpress.org/bernhard-reiter/)(
1), [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) (1), [@tw2113](https://profiles.wordpress.org/tw2113/)(
1), [@Nikschavan](https://profiles.wordpress.org/nikschavan/) (1), [@keyur5](https://profiles.wordpress.org/keyur5/)(
1), [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) (1), [@jdy68](https://profiles.wordpress.org/jdy68/)(
1), [@dgwyer](https://profiles.wordpress.org/dgwyer/) (1), [@almendron](https://profiles.wordpress.org/almendron/)(
1), [@kallookoo](https://profiles.wordpress.org/kallookoo/) (1), [@zieladam](https://profiles.wordpress.org/zieladam/)(
1), [@palmiak](https://profiles.wordpress.org/palmiak/) (1), [@andraganescu](https://profiles.wordpress.org/andraganescu/)(
1), [@dingo_d](https://profiles.wordpress.org/dingo_d/) (1), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)(
1), [@utz119](https://profiles.wordpress.org/utz119/) (1), [@kadamwhite](https://profiles.wordpress.org/kadamwhite/)(
1), [@scruffian](https://profiles.wordpress.org/scruffian/) (1), [@NateWr](https://profiles.wordpress.org/natewr/)(
1), [@schlessera](https://profiles.wordpress.org/schlessera/) (1), [@Spacedmonkey](https://profiles.wordpress.org/spacedmonkey/)(
1), [@ribaricplusplus](https://profiles.wordpress.org/ribaricplusplus/) (1), [@talldanwp](https://profiles.wordpress.org/talldanwp/)(
1), [@wpscholar](https://profiles.wordpress.org/wpscholar/) (1), @pgking (1), [@andynick](https://profiles.wordpress.org/andynick/)(
1), [@richtabor](https://profiles.wordpress.org/richtabor/) (1), [@kraftbj](https://profiles.wordpress.org/kraftbj/)(
1), [@dimadin](https://profiles.wordpress.org/dimadin/) (1), [@gregrickaby](https://profiles.wordpress.org/gregrickaby/)(
1), [@ellenbauer](https://profiles.wordpress.org/ellenbauer/) (1), [@jffng](https://profiles.wordpress.org/jffng/)(
1), [@dansoschin](https://profiles.wordpress.org/dansoschin/) (1), [@karmatosed](https://profiles.wordpress.org/karmatosed/)(
1), [@littlebigthing](https://profiles.wordpress.org/littlebigthing/) (1), [@williampatton](https://profiles.wordpress.org/williampatton/)(
1), [@onemaggie](https://profiles.wordpress.org/onemaggie/) (1), [@matveb](https://profiles.wordpress.org/matveb/)(
1), [@mburridge](https://profiles.wordpress.org/mburridge/) (1), [@mtoensing](https://profiles.wordpress.org/mtoensing/)(
1), [@nickcernis](https://profiles.wordpress.org/nickcernis/) (1), [@nielslange](https://profiles.wordpress.org/nielslange/)(
1), [@wparslan](https://profiles.wordpress.org/wparslan/) (1), [@georgestephanis](https://profiles.wordpress.org/georgestephanis/)(
1), [@davidkryzaniak](https://profiles.wordpress.org/davidkryzaniak/) (1), [@lukecarbis](https://profiles.wordpress.org/lukecarbis/)(
1), [@galbaras](https://profiles.wordpress.org/galbaras/) (1), [@jdgrimes](https://profiles.wordpress.org/jdgrimes/)(
1), [@justindocanto](https://profiles.wordpress.org/justindocanto/) (1), [@kwisatz](https://profiles.wordpress.org/kwisatz/)(
1), [@liammitchell](https://profiles.wordpress.org/liammitchell/) (1), [@lucasw89](https://profiles.wordpress.org/lucasw89/)(
1), [@nettsite](https://profiles.wordpress.org/nettsite/) (1), [@dpegasusm](https://profiles.wordpress.org/dpegasusm/)(
1), [@nlpro](https://profiles.wordpress.org/nlpro/) (1), [@procodewp](https://profiles.wordpress.org/procodewp/)(
1), [@psufan](https://profiles.wordpress.org/psufan/) (1), [@richardfoley](https://profiles.wordpress.org/richardfoley/)(
1), [@skunkbad](https://profiles.wordpress.org/skunkbad/) (1), [@travisnorthcutt](https://profiles.wordpress.org/travisnorthcutt/)(
1), [@fpcsjames](https://profiles.wordpress.org/fpcsjames/) (1), [@asif2bd](https://profiles.wordpress.org/asif2bd/)(
1), [@zoiec](https://profiles.wordpress.org/zoiec/) (1), [@ianhayes94](https://profiles.wordpress.org/ianhayes94/)(
1), [@david](https://profiles.wordpress.org/david/).binda (1), [@mista-flo](https://profiles.wordpress.org/mista-flo/)(
1), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) (1), [@bravokeyl](https://profiles.wordpress.org/bravokeyl/)(
1), [@gkloveweb](https://profiles.wordpress.org/gkloveweb/) (1), [@hitendra-chopda](https://profiles.wordpress.org/hitendra-chopda/)(
1), [@ovann86](https://profiles.wordpress.org/ovann86/) (1), [@anthonyeden](https://profiles.wordpress.org/anthonyeden/)(
1), [@pankajmohale](https://profiles.wordpress.org/pankajmohale/) (1), [@sabrib](https://profiles.wordpress.org/sabrib/)(
1), [@xkon](https://profiles.wordpress.org/xkon/) (1), [@dlt101](https://profiles.wordpress.org/dlt101/)(
1), [@mnelson4](https://profiles.wordpress.org/mnelson4/) (1), [@datainterlock](https://profiles.wordpress.org/datainterlock/)(
1), [@anandau14](https://profiles.wordpress.org/anandau14/) (1), [@woodyhayday](https://profiles.wordpress.org/woodyhayday/)(
1), [@henrywright](https://profiles.wordpress.org/henrywright/) (1), [@aadilali](https://profiles.wordpress.org/aadilali/)(
1), [@jeremyescott](https://profiles.wordpress.org/jeremyescott/) (1), [@davidmosterd](https://profiles.wordpress.org/davidmosterd/)(
1), [@herregroen](https://profiles.wordpress.org/herregroen/) (1), [@michelwppi](https://profiles.wordpress.org/michelwppi/)(
1), [@kebbet](https://profiles.wordpress.org/kebbet/) (1), [@iaaxpage](https://profiles.wordpress.org/iaaxpage/)(
1), [@mclaurent](https://profiles.wordpress.org/mclaurent/) (1), [@theMikeD](https://profiles.wordpress.org/themiked/)(
1), [@paulschreiber](https://profiles.wordpress.org/paulschreiber/) (1), [@jeremyfelt](https://profiles.wordpress.org/jeremyfelt/)(
1), [@dontgo2sleep](https://profiles.wordpress.org/dontgo2sleep/) (1), [@swb1192](https://profiles.wordpress.org/swb1192/)(
1), [@afragen](https://profiles.wordpress.org/afragen/) (1), [@JeffPaul](https://profiles.wordpress.org/jeffpaul/)(
1), [@Collizo4sky](https://profiles.wordpress.org/collizo4sky/) (1), [@antpb](https://profiles.wordpress.org/antpb/)(
1), [@hasanuzzamanshamim](https://profiles.wordpress.org/hasanuzzamanshamim/) (1),
[@jigneshnakrani](https://profiles.wordpress.org/jigneshnakrani/) (1), [@sourovroy](https://profiles.wordpress.org/sourovroy/)(
1), [@rachelbaker](https://profiles.wordpress.org/rachelbaker/) (1), [@soniakash](https://profiles.wordpress.org/soniakash/)(
1), [@benitolopez](https://profiles.wordpress.org/benitolopez/) (1), [@danielbachhuber](https://profiles.wordpress.org/danielbachhuber/)(
1), [@PieWP](https://profiles.wordpress.org/piewp/) (1), [@szaqal21](https://profiles.wordpress.org/szaqal21/)(
1), [@mjulian7](https://profiles.wordpress.org/mjulian7/) (1), [@pputzer](https://profiles.wordpress.org/pputzer/)(
1), [@mamaduka](https://profiles.wordpress.org/mamaduka/) (1), [@karpstrucking](https://profiles.wordpress.org/karpstrucking/)(
1), [@mcjambi](https://profiles.wordpress.org/mcjambi/) (1), [@ashfame](https://profiles.wordpress.org/ashfame/)(
1), [@annezazu](https://profiles.wordpress.org/annezazu/) (1), [@calebwoodbridge](https://profiles.wordpress.org/calebwoodbridge/)(
1), [@guillaumeturpin](https://profiles.wordpress.org/guillaumeturpin/) (1), and
[@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/) (1).

**Congrats and welcome to our 36 (!!) new contributors of the week: **[@manishamakhija](https://profiles.wordpress.org/manishamakhija/),
[@rviscomi](https://profiles.wordpress.org/rviscomi/), @briceduclos, [@keyur5](https://profiles.wordpress.org/keyur5/),
[@kallookoo](https://profiles.wordpress.org/kallookoo/), @pgking, [@andynick](https://profiles.wordpress.org/andynick/),
[@dansoschin](https://profiles.wordpress.org/dansoschin/), [@mburridge](https://profiles.wordpress.org/mburridge/),
[@mtoensing](https://profiles.wordpress.org/mtoensing/), [@nickcernis](https://profiles.wordpress.org/nickcernis/),
[@wparslan](https://profiles.wordpress.org/wparslan/), [@justindocanto](https://profiles.wordpress.org/justindocanto/),
[@kwisatz](https://profiles.wordpress.org/kwisatz/), [@liammitchell](https://profiles.wordpress.org/liammitchell/),
[@lucasw89](https://profiles.wordpress.org/lucasw89/), [@nettsite](https://profiles.wordpress.org/nettsite/),
[@dpegasusm](https://profiles.wordpress.org/dpegasusm/), [@psufan](https://profiles.wordpress.org/psufan/),
[@skunkbad](https://profiles.wordpress.org/skunkbad/), [@zoiec](https://profiles.wordpress.org/zoiec/),
[@ianhayes94](https://profiles.wordpress.org/ianhayes94/), [@anthonyeden](https://profiles.wordpress.org/anthonyeden/),
[@sabrib](https://profiles.wordpress.org/sabrib/), [@dlt101](https://profiles.wordpress.org/dlt101/),
[@datainterlock](https://profiles.wordpress.org/datainterlock/), [@woodyhayday](https://profiles.wordpress.org/woodyhayday/),
[@aadilali](https://profiles.wordpress.org/aadilali/), [@mclaurent](https://profiles.wordpress.org/mclaurent/),
[@dontgo2sleep](https://profiles.wordpress.org/dontgo2sleep/), [@swb1192](https://profiles.wordpress.org/swb1192/),
[@hasanuzzamanshamim](https://profiles.wordpress.org/hasanuzzamanshamim/), [@benitolopez](https://profiles.wordpress.org/benitolopez/),
[@mjulian7](https://profiles.wordpress.org/mjulian7/), [@mcjambi](https://profiles.wordpress.org/mcjambi/),
[@calebwoodbridge](https://profiles.wordpress.org/calebwoodbridge/). ♥️

**Core committers:** [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)(
23), [@desrosj](https://profiles.wordpress.org/desrosj/) (18), [@noisysocks](https://profiles.wordpress.org/noisysocks/)(
14), [@joedolson](https://profiles.wordpress.org/joedolson/) (12), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
8), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) (7), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/)(
6), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (5), [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/)(
5), [@westonruter](https://profiles.wordpress.org/westonruter/) (4), [@johnjamesjacoby](https://profiles.wordpress.org/johnjamesjacoby/)(
2), [@jorbin](https://profiles.wordpress.org/jorbin/) (1), [@johnbillion](https://profiles.wordpress.org/johnbillion/)(
1), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) (1), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)(
1), [@ocean90](https://profiles.wordpress.org/ocean90/) (1), [@youknowriad](https://profiles.wordpress.org/youknowriad/)(
1), [@flixos90](https://profiles.wordpress.org/flixos90/) (1), [@antpb](https://profiles.wordpress.org/antpb/)(
1), [@jffng](https://profiles.wordpress.org/jffng/) (1), and [@ryelle](https://profiles.wordpress.org/ryelle/)(
1).

[#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-9](https://make.wordpress.org/core/tag/5-9/),
[#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/)

 [  ](https://profiles.wordpress.org/hellofromtonya/) [Tonya Mork](https://profiles.wordpress.org/hellofromtonya/)
9:33 pm _on_ November 16, 2021     
Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/)

# 󠀁[WordPress 5.9 Beta 1 will be delayed for 24 hours](https://make.wordpress.org/core/2021/11/16/wordpress-5-9-beta-1-will-be-delayed-for-24-hours/)󠁿

Updated on Nov 17th: List of tickets/issues shared.

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 [was scheduled](https://make.wordpress.org/core/5-9/)
for release today.

A flag was raised in [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7/p1637018865252000)
that is considered a blockerblocker A bug which is so severe that it blocks a release.
for the Beta phase. There are a few minor flags that need to be prioritized for 
Beta 2 and beyond. ~A list of tickets/issues is being prepared to add to GitHubGitHub
GitHub is a website that offers online implementation of git repositories that can
easily be shared, copied and modified by other developers. Public repositories are
free to host, private repositories require a paid subscription. GitHub introduced
the concept of the ‘pull request’ where code changes done in branches by contributors
can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/),
and this post will be updated with that information as it becomes available.~ [A list of tickets/issues](https://github.com/WordPress/gutenberg/issues/36556)
is being assessed to determine which are blockers for Beta 1.

Beta 1 is now delayed by one day. The release team anticipates starting the process
on [Wednesday, November 17, 2021 at 21:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211117T2100).
That’s immediately after the weekly CoreCore Core is the set of software required
to run WordPress. The Core Development Team builds WordPress. developers’ chat, 
in the Core channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

It’s the last opportunity for tickets to land in 5.9. After Beta 1, any tickets 
not committed will move to 6.0 or future releases.

The rest of the 5.9 release cycle schedule is unchanged.

[#5-9](https://make.wordpress.org/core/tag/5-9/)

 [  ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)
9:50 pm _on_ November 15, 2021     
Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/),
[core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/),
[meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)   

# 󠀁[Editor Chat Agenda: 17 November 2021](https://make.wordpress.org/core/2021/11/15/editor-chat-agenda-17-november-2021/)󠁿

Facilitator and notetaker: [@paaljoachim](https://profiles.wordpress.org/paaljoachim/)

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, November 17 2021, 03:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20211117T15&p1=187&ah=1).

_This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7)
channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform
[https://slack.com/](https://slack.com/). The WordPress community has its own Slack
Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._

 * [Gutenberg 12.1 RC1](https://github.com/WordPress/gutenberg/releases/tag/v12.1.0-rc.1)
   will be released Wednesday.
 * 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 is [delayed by 24 hours](https://make.wordpress.org/core/2021/11/16/wordpress-5-9-beta-1-will-be-delayed-for-24-hours/)
   and will be released 17 November.
 * [WordPress 5.9](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/)
   roadmap and [priorities](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/).
 * Updates based on [updated scope for site editing projects](https://github.com/WordPress/gutenberg/issues/33094):
    - Navigation BlockBlock Block is the abstract term used to describe units of
      markup that, composed together, form the content or layout of a webpage using
      the WordPress editor. The idea combines concepts of what in the past may have
      achieved with shortcodes, custom HTML, and embed discovery into a single consistent
      API and user experience. & Navigation Editor.
    - Template editor.
    - Patterns.
    - Styling.
    - Mobile Team.
 * Task Coordination.
 * Open Floor.

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](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/),
[#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), 
[#meeting](https://make.wordpress.org/core/tag/meeting/)

 [  ](https://profiles.wordpress.org/justinahinon/) [Justin Ahinon](https://profiles.wordpress.org/justinahinon/)
12:04 pm _on_ November 15, 2021     
Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/),
[meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 414 )](https://make.wordpress.org/core/tag/performance/),
[performance-chat ( 341 )](https://make.wordpress.org/core/tag/performance-chat/)

# 󠀁[Performance Chat Agenda: November 16, 2021](https://make.wordpress.org/core/2021/11/15/performance-chat-agenda-november-16-2021/)󠁿

Here is the agenda for this week’s performance team meeting to occur on [November 16 2021, at 15:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211116T1500).

## Focus group projects discussion

Over the current meeting and the next one (November 23), we will allocate 30 minutes
for each focus group to share and discuss their plans with the overall performance
team.

## Weekly meeting time

Currently, our weekly meetings are held at the same time as the 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](https://www.javascript.com/)
and Themes team meetings. With several interested people unable to attend.

One option would be to hold our meetings an hour later, so at 4:00 PM UTC. What 
do you think about this?

_This meeting happens in the [#performance](https://wordpress.slack.com/archives/C02KGN5K076)
channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/)._

[#agenda](https://make.wordpress.org/core/tag/agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/),
[#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/)

 [  ](https://profiles.wordpress.org/andrewserong/) [Andrew Serong](https://profiles.wordpress.org/andrewserong/)
12:48 am _on_ November 12, 2021     
Tags: [block-editor ( 139 )](https://make.wordpress.org/core/tag/block-editor/),
[core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/),
[gutenberg-new ( 216 )](https://make.wordpress.org/core/tag/gutenberg-new/)   

# 󠀁[What’s new in Gutenberg 11.9.0 (10 November)](https://make.wordpress.org/core/2021/11/12/whats-new-in-gutenberg-11-9-0-10-november/)󠁿

It’s now November, which means this is the final GutenbergGutenberg The Gutenberg
project is the new Editor Interface for WordPress. The editor improves the process
and experience of creating new content, making writing rich content much simpler.
It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
release for [WordPress 5.9](https://make.wordpress.org/core/5-9/)! Included are 
several new Gutenberg blocks for working with post comments, along with a host of
enhancements to existing blocks with a lot of focus going into improving the Navigation
blockBlock Block is the abstract term used to describe units of markup that, composed
together, form the content or layout of a webpage using the WordPress editor. The
idea combines concepts of what in the past may have achieved with shortcodes, custom
HTML, and embed discovery into a single consistent API and user experience., which
will feature heavily in block themes.

## Finalizing the Site Editing entry point

In preparation to introduce Site Editing in WordPress 5.9 and following the [site editing IA proposal](https://make.wordpress.org/design/2021/10/15/site-editing-ia-concepts-how-to-surface-and-access-new-features/),
the Site Editor menu item has been renamed to “Editor”, and now [sits under the Appearance menu](https://github.com/WordPress/gutenberg/pull/36064).

[[

## Fullscreen pattern explorer modal

With the increasing number of block patterns available in the pattern directory 
and bundled with themes, there is now a full-screen modal [pattern explorer](https://github.com/WordPress/gutenberg/pull/35773)
that can be accessed via an Explore button in the pattern inserter. This explorer
allows users to find patterns in a bigger, more advanced tool.

## New comment blocks

This release includes a handful of new blocks to allow for granular control over
the design of comments in templates for posts. The new [Comments Query Loop and Comment Template blocks](https://github.com/WordPress/gutenberg/pull/35231)
work similarly to the 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](https://codex.wordpress.org/The_Loop)
and Post Template blocks, but for the display of comments via a default template
composed of Post Comment Author, Post Comment Date, and Post Comment Content blocks.
Site owners can lay out the blocks to suit their designs, for example, by including
the newly added [Comment Author Avatar block](https://github.com/WordPress/gutenberg/pull/35396).

Outside of the display of the comments themselves, are two blocks for displaying
the [Comment Reply Link](https://github.com/WordPress/gutenberg/pull/35774) and 
[Edit Comment Link](https://github.com/WordPress/gutenberg/pull/35965).

With these new blocks now available, the existing experimental Post Comment block
[has been deprecated](https://github.com/WordPress/gutenberg/pull/36032), with the
block now hidden in the inserter.

## Further iterations on the Navigation block

With its inclusion in 5.9 and all its recent enhancements, the Navigation block 
is no longer considered experimental. The block has now opted-in to the [flex layout block support](https://github.com/WordPress/gutenberg/pull/36169),
the placeholder for the block [has been simplified](https://github.com/WordPress/gutenberg/pull/36023),
and the UIUI User interface and naming of navigation entities [have been refined](https://github.com/WordPress/gutenberg/pull/36238).
The data layer for the Navigation block has also been improved, as the block’s data
is [now saved](https://github.com/WordPress/gutenberg/pull/35746) to a `wp_navigation`
custom post typeCustom Post Type WordPress can hold and display many different types
of content. A single item of such a content is generally called a post, although
post is also a specific post type. Custom Post Types gives your site the ability
to have templated posts, to simplify the concept., allowing greater flexibility 
surrounding the management of navigation menus used for this block. Among these 
management improvements, there is an additional menu item for editing and managing
navigation menus, found under the Appearance tab, and it is now also possible to
[create new menus](https://github.com/WordPress/gutenberg/pull/36245) from an existing
Navigation block directly within the editor.

[[

## Typography tools enhancements

The Typography controls for blocks have been switched to use the ToolsPanel component,
which allows blocks’ frequently used settings to be displayed by default, with more
advanced controls able to be exposed via a menu. With this in place, typography 
support across the whole block library [has been updated](https://github.com/WordPress/gutenberg/pull/34064),
with many blocks now opting into more controls. For example, most text-based blocks
like paragraph, heading, and list blocks now support font style, letter spacing,
and text transform, with only the most common font size displayed by default.

## 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

Performance and accessibility of the [block list view](https://github.com/WordPress/gutenberg/pull/35230)
have been improved by using a windowing technique that now renders a fixed number
of items at a time instead of every block. The [post title](https://github.com/WordPress/gutenberg/pull/35898)
component is now covered for screen readers, and [announcements have been added](https://github.com/WordPress/gutenberg/pull/35896)
on formatting changes in rich text fields. Also, the “Save” [keyboard shortcut](https://github.com/WordPress/gutenberg/pull/36138)
has been rolled out to the site editor.

## Other Notable Highlights

As part of contributors’ efforts to provide an outstanding editor performance, the
[initial loading of the site editor](https://github.com/WordPress/gutenberg/pull/36044)
has been improved. A few features common to the block editor have now been rolled
out to the site editor, including [rich previews](https://github.com/WordPress/gutenberg/pull/35951)
in the link editing UI, which also features [an extra text field](https://github.com/WordPress/gutenberg/pull/33849)
when modifying an existing link. The [UI for saving multiple entities](https://github.com/WordPress/gutenberg/pull/35933)(
e.g. site, template, and template parts) has also been improved with descriptive
text added.

[[

Block enhancements include [padding support](https://github.com/WordPress/gutenberg/pull/35701)
for the Columns block, and the [Post Author](https://github.com/WordPress/gutenberg/pull/35963),
[Post Excerpt](https://github.com/WordPress/gutenberg/pull/35959), [Comment Author](https://github.com/WordPress/gutenberg/pull/36213),
and [Code](https://github.com/WordPress/gutenberg/pull/27582) blocks now all have
spacing support. Support for [embedding Wolfram Cloud](https://github.com/WordPress/gutenberg/pull/35656)
links has been added, and there is now [transparency support](https://github.com/wordpress/gutenberg/pull/34130)
in the Duotone filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/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. that can be applied to images.

In 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. changes, there is a proposed new [set of functions](https://github.com/WordPress/gutenberg/pull/34843)
to make it easier for plugins and themes to extract data from `theme.json` settings
and styles without having to use `WP_Theme_JSON_Resolver`. Also, usage of `InnerBlocks.
Content` within blocks’ save functions [has been replaced](https://github.com/WordPress/gutenberg/pull/26031)
with `useInnerBlocksProps.save` for better consistency with behavior in edit components.

The full set of changes included in this release can be found below.

## Gutenberg 11.9.0

### Features

#### Block Library

 * New Block: Comment Reply Link. ([35774](https://github.com/WordPress/gutenberg/pull/35774))
 * New Block: Comment Link. ([35965](https://github.com/WordPress/gutenberg/pull/35965))
 * New Block: Comment 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.. ([35396](https://github.com/WordPress/gutenberg/pull/35396))
 * New Block: Comments Query Loop. ([35231](https://github.com/WordPress/gutenberg/pull/35231))

### Enhancements

#### Block Library

 * Buttons: Add flex layout and new layout type. ([35819](https://github.com/WordPress/gutenberg/pull/35819))
 * Code: Add support for padding, color, and border styles. ([27582](https://github.com/WordPress/gutenberg/pull/27582))
 * Columns: Add padding support. ([35701](https://github.com/WordPress/gutenberg/pull/35701))
 * Comment Author Name: Add spacing to have same options as Post Author Name. ([36213](https://github.com/WordPress/gutenberg/pull/36213))
 * Comment Edit Link: Add alignment option. ([36033](https://github.com/WordPress/gutenberg/pull/36033))
 * Embed: Add Wolfram Cloud as an embed provider. ([35656](https://github.com/WordPress/gutenberg/pull/35656))
 * Gallery: Replace gallery experimental setting with a check for use_balanceTags.(
   [34979](https://github.com/WordPress/gutenberg/pull/34979))
 * Image: Add data-id attribute on server side render for coreCore Core is the set
   of software required to run WordPress. The Core Development Team builds WordPress.
   galleries. ([35975](https://github.com/WordPress/gutenberg/pull/35975))
 * Navigation: Add create new menu button. ([36245](https://github.com/WordPress/gutenberg/pull/36245))
 * Navigation: Add delete nav menu button. ([35981](https://github.com/WordPress/gutenberg/pull/35981))
 * Navigation: Add featured transforms in Link Control for Navigation Link items.(
   [35857](https://github.com/WordPress/gutenberg/pull/35857))
 * Navigation: Add flex layout. ([36169](https://github.com/WordPress/gutenberg/pull/36169))
 * Navigation: Add missing menu item attributes. ([35634](https://github.com/WordPress/gutenberg/pull/35634))
 * Navigation: Create nav menu on pattern insertion or when the block has uncontrolled
   inner blocks. ([36024](https://github.com/WordPress/gutenberg/pull/36024))
 * Navigation: Migrate classic menus to block-based menus on theme switch. ([36255](https://github.com/WordPress/gutenberg/pull/36255))
 * Navigation: Mobile responsive navigation by default. ([35917](https://github.com/WordPress/gutenberg/pull/35917))
 * Navigation: Provide a way to manage wp_navigation posts from wp-adminadmin (and
   super admin). ([36126](https://github.com/WordPress/gutenberg/pull/36126))
 * Navigation: Reword navigation color labels. ([35916](https://github.com/WordPress/gutenberg/pull/35916))
 * Navigation: Save data to a wp_navigation post type. ([35746](https://github.com/WordPress/gutenberg/pull/35746))
 * Navigation: Show the placeholder again when moving from a valid menu to non-existing
   menu. ([36210](https://github.com/WordPress/gutenberg/pull/36210))
 * Navigation: Update block entity automatic name generation and refine naming UI.(
   [36238](https://github.com/WordPress/gutenberg/pull/36238))
 * Navigation: Use a single placeholder for the block. ([36023](https://github.com/WordPress/gutenberg/pull/36023))
 * Page List: Create a JSJS JavaScript, a web scripting language typically executed
   in the browser. Often used for advanced user interfaces and behaviors. version
   for the editor. ([31670](https://github.com/WordPress/gutenberg/pull/31670))
 * Post Author: Add spacing controls. ([35963](https://github.com/WordPress/gutenberg/pull/35963))
 * Post Comment: Deprecate the block now that the Comment Query Loop block has been
   added. ([36032](https://github.com/WordPress/gutenberg/pull/36032))
 * Post Comment Author: Add alignment options. ([36045](https://github.com/WordPress/gutenberg/pull/36045))
 * Post Comments: Even out the top margin inside the block. ([35887](https://github.com/WordPress/gutenberg/pull/35887))
 * Post Comments: Hide the “Comments Closed” message. ([35743](https://github.com/WordPress/gutenberg/pull/35743))
 * Post Comment Form: Adds in basic styling for post comment form. ([35704](https://github.com/WordPress/gutenberg/pull/35704))
 * Post ExcerptExcerpt An excerpt is the description of the blog post or page that
   will by default show on the blog archive page, in search results (SERPs), and
   on social media. With an SEO plugin, the excerpt may also be in that plugin’s
   metabox.: Add spacing controls. ([35959](https://github.com/WordPress/gutenberg/pull/35959))
 * Post Excerpt: Don’t print the wrapper when there is no excerpt. ([35749](https://github.com/WordPress/gutenberg/pull/35749))
 * Post Title: Return no markup if title is empty. ([35861](https://github.com/WordPress/gutenberg/pull/35861))
 * Search: Add contextual defaults when inserted in Navigation block. ([36125](https://github.com/WordPress/gutenberg/pull/36125))
 * Gallery block: Add a dismissible warning about the need for versions >=18.2 of
   the mobile app. ([36012](https://github.com/WordPress/gutenberg/pull/36012))

#### Accessibility

 * Add announcement on formatting change for screen readers. ([35896](https://github.com/WordPress/gutenberg/pull/35896))
 * Add aria-current to navigation link, submenu, page list. ([35880](https://github.com/WordPress/gutenberg/pull/35880))
 * Link editing: Improve focus styles for Link UI preview title. ([35853](https://github.com/WordPress/gutenberg/pull/35853))
 * Site Editor: Enable the “Save” keyboard shortcut. ([36138](https://github.com/WordPress/gutenberg/pull/36138))
 * Try to communicate to screen readers that post title is textarea. ([35898](https://github.com/WordPress/gutenberg/pull/35898))

#### Block Editor

 * Block toolbar: Remove visual clue from text alignment icon. ([35922](https://github.com/WordPress/gutenberg/pull/35922))
 * Drag and drop: Show drag slot instead of hiding the block being dragged. ([33950](https://github.com/WordPress/gutenberg/pull/33950))
 * Enable rich previews in the Link UI for the Site Editor. ([35951](https://github.com/WordPress/gutenberg/pull/35951))
 * Link editing: Update Link UI design for preview action buttons to use icons for
   edit and unlink. ([35833](https://github.com/WordPress/gutenberg/pull/35833))
 * Multi-Entity Saving UI Improvements. ([35933](https://github.com/WordPress/gutenberg/pull/35933))
 * Use the block’s name in the “remove block” menu item in the block settings dropdown.(
   [35872](https://github.com/WordPress/gutenberg/pull/35872))
 * StripHTML: preserve leading and trailing spaces and strip script and on* attributes.(
   [35539](https://github.com/WordPress/gutenberg/pull/35539))

#### Full Site Editing

 * Improve the initial loading of the site editor. ([36044](https://github.com/WordPress/gutenberg/pull/36044))
 * Move the Site Editor menu item to sit under Appearance and rename to Editor. (
   [36064](https://github.com/WordPress/gutenberg/pull/36064))
 * Remove navigation panel in site editor. ([36194](https://github.com/WordPress/gutenberg/pull/36194))
 * Use Heading component on NavigationMenu and NavigationGroup components. ([36009](https://github.com/WordPress/gutenberg/pull/36009))
 * Use SearchControl component inside nav menu. ([36011](https://github.com/WordPress/gutenberg/pull/36011))

#### Components

 * ColorPicker: Implement new color palette editor component. ([35783](https://github.com/WordPress/gutenberg/pull/35783))
 * Duotone: Add description to clarify that the underlying image will not be affected.(
   [36018](https://github.com/WordPress/gutenberg/pull/36018))
 * Modal: Wrap the modal contents in a StyleProvider. ([36261](https://github.com/WordPress/gutenberg/pull/36261))
 * ToolsPanel: Update typography panel layout. ([35911](https://github.com/WordPress/gutenberg/pull/35911))
 * LinkControl: Split control for URLURL A specific web address of a website or 
   web page on the Internet, such as a website’s URL www.wordpress.org and Text 
   within Link UI. ([33849](https://github.com/WordPress/gutenberg/pull/33849))

#### Template Editor

 * Add resizer to template part focus mode. ([35728](https://github.com/WordPress/gutenberg/pull/35728))
 * Auto resize the height of template part focus mode. ([35974](https://github.com/WordPress/gutenberg/pull/35974))

#### Global Styles

 * Remove the duplicated title in background, text and link views. ([35583](https://github.com/WordPress/gutenberg/pull/35583))
 * Typography: Switch to ToolsPanel for block support UI. ([33744](https://github.com/WordPress/gutenberg/pull/33744))
 * Add a Global Styles endpoint and use it in the site editor. ([35801](https://github.com/WordPress/gutenberg/pull/35801))
 * Migrate 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. v1 to v2. ([36155](https://github.com/WordPress/gutenberg/pull/36155))
 * Update: Show all color and gradient origins (core, theme, and user). ([35970](https://github.com/WordPress/gutenberg/pull/35970))

#### Design Tools

 * Duotone: Enable transparency. ([34130](https://github.com/WordPress/gutenberg/pull/34130))
 * Layout: Add `flex-wrap` control to `flex` layout. ([36003](https://github.com/WordPress/gutenberg/pull/36003))
 * Typography block support: Add typography support and defaults. ([34064](https://github.com/WordPress/gutenberg/pull/34064))

#### Media

 * Remove “security” verbiage from warning when filetype does not pass on upload.(
   [36226](https://github.com/WordPress/gutenberg/pull/36226))

#### Patterns

 * Add an `inserter` flag to hide patterns from UI. ([36108](https://github.com/WordPress/gutenberg/pull/36108))

#### Themes

 * Remove experimental feature notice for block themes. ([36083](https://github.com/WordPress/gutenberg/pull/36083))

#### General Interface

 * Apply borders to canvas rather than other UI elements. ([31081](https://github.com/WordPress/gutenberg/pull/31081))

#### REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) 󠀁[https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)󠁿

 * Respect fields param for global styles REST API requests. ([36206](https://github.com/WordPress/gutenberg/pull/36206))
 * URL Details: Update regex to include `og:Description`. ([35875](https://github.com/WordPress/gutenberg/pull/35875))

### New APIs

#### Global Styles

 * Add API to access global settings, styles, and stylesheet. ([34843](https://github.com/WordPress/gutenberg/pull/34843))

#### Block Library

 * Inner blocks: Add `useInnerBlocksProps.save` function for edit/save symmetry,
   and stabilise API. ([26031](https://github.com/WordPress/gutenberg/pull/26031))

### Bug Fixes

#### Block Library

 * Buttons: Address deprecation issues from Buttons flex layout PR. ([36192](https://github.com/WordPress/gutenberg/pull/36192))
 * Classic: Fix select all blocks side effect that overwrote paragraph block contents.(
   [35999](https://github.com/WordPress/gutenberg/pull/35999))
 * Column: Only add flex-basis if width contains a number. ([35831](https://github.com/WordPress/gutenberg/pull/35831))
 * Comment Template: Move inner blocks container to separate components. ([36174](https://github.com/WordPress/gutenberg/pull/36174))
 * Blocks: Fix relative URLs for inlined styles. ([35538](https://github.com/WordPress/gutenberg/pull/35538))
 * Navigation: Disable ability to edit wp_navigation menus via `Appearance -> Navigation
   Menus` for non-FSE themes. ([36257](https://github.com/WordPress/gutenberg/pull/36257))
 * Fix incorrect attributes definitions. ([36264](https://github.com/WordPress/gutenberg/pull/36264))
 * Fix saving template parts in the site editor by fixing controlled inner blocks
   parent block attributes updates. ([35827](https://github.com/WordPress/gutenberg/pull/35827))
 * Fix incorrect attributes definitions for Column, Cover, and Group blocks. ([36140](https://github.com/WordPress/gutenberg/pull/36140))
 * Gallery: Make sure the mobile warning notice only runs when images are added 
   to a new block. ([36326](https://github.com/WordPress/gutenberg/pull/36326))
 * Gallery: Only show the gallery upload error message if mixed multiple files are
   uploaded. ([35790](https://github.com/WordPress/gutenberg/pull/35790))
 * Gallery: Remove the arbitrary alt text that is added to gallery images. ([35936](https://github.com/WordPress/gutenberg/pull/35936))
 * Group: Fix inner container regexes that relied on fixed div 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.). ([36256](https://github.com/WordPress/gutenberg/pull/36256))
 * Heading: Avoid error on split when the paragraph isn’t registered. ([35871](https://github.com/WordPress/gutenberg/pull/35871))
 * Image: Make sure the Image block border radius is inherited if the image is linked.(
   [36289](https://github.com/WordPress/gutenberg/pull/36289))
 * Navigation Submenu: Fix PHPPHP The web scripting language in which WordPress 
   is primarily architected. WordPress requires PHP 7.4 or higher notice caused 
   by stale id reference. ([35984](https://github.com/WordPress/gutenberg/pull/35984))
 * Navigation overlay menu: Fix submenu spacing. ([35823](https://github.com/WordPress/gutenberg/pull/35823))
 * Navigation: Ensure menus exist before map operation. ([36355](https://github.com/WordPress/gutenberg/pull/36355))
 * Navigation: Fix accessibility issues. ([36292](https://github.com/WordPress/gutenberg/pull/36292))
 * Navigation: Fix dropdown indicator position. ([36106](https://github.com/WordPress/gutenberg/pull/36106))
 * Navigation: Fix issues with responsive justifications. ([35913](https://github.com/WordPress/gutenberg/pull/35913))
   and ([36105](https://github.com/WordPress/gutenberg/pull/36105))
 * Navigation: Fix padding for social links on mobile. ([35824](https://github.com/WordPress/gutenberg/pull/35824))
 * Navigation: Fix submenus not opening on click. ([36290](https://github.com/WordPress/gutenberg/pull/36290))
 * Navigation: Hide post attributes 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. box. ([36358](https://github.com/WordPress/gutenberg/pull/36358))
 * Navigation: Small styling fixes and tweaks. ([36298](https://github.com/WordPress/gutenberg/pull/36298))
 * Pattern: Remove wrapping div. ([36090](https://github.com/WordPress/gutenberg/pull/36090))
 * Post Comment: Handle the case where a comment does not exist. ([35810](https://github.com/WordPress/gutenberg/pull/35810))
 * Post Navigation Link: Do not translate HTMLHTML HyperText Markup Language. The
   semantic scripting language primarily used for outputting content in web browsers.
   tag. ([35930](https://github.com/WordPress/gutenberg/pull/35930))
 * Post Template Block: Move inner blocks container to separate component. ([35945](https://github.com/WordPress/gutenberg/pull/35945))
 * Post Terms: Prevent the block from breaking on pages. ([35957](https://github.com/WordPress/gutenberg/pull/35957))
 * Site Logo: Fix center alignment. ([35971](https://github.com/WordPress/gutenberg/pull/35971))
 * Site Logo: Fix fatal error in Site Logo block in WP 5.9. ([36195](https://github.com/WordPress/gutenberg/pull/36195))
 * Prevent PHP notice in Elements block support for blocks with empty content. (
   [35836](https://github.com/WordPress/gutenberg/pull/35836))

#### Components

 * AnglePickerControl: Use admin color scheme. ([35908](https://github.com/WordPress/gutenberg/pull/35908))
 * BaseControl: Fix undefined Help text id if no id is passed to component. ([35899](https://github.com/WordPress/gutenberg/pull/35899))
 * ColorListPicker: Fix spacing to accomodate the new color picker. ([36017](https://github.com/WordPress/gutenberg/pull/36017))
 * ColorPalette: Fix className. ([36016](https://github.com/WordPress/gutenberg/pull/36016))
 * ColorPicker: Fix unexpected movements, and closing on first click in the color
   picker. ([35670](https://github.com/WordPress/gutenberg/pull/35670))
 * Popover: Check anchorDocument default view before removing events. ([35832](https://github.com/WordPress/gutenberg/pull/35832))
 * RangeControl: Fix style issue in RTL. ([35777](https://github.com/WordPress/gutenberg/pull/35777))
 * Storybook: Lazy load LTR/RTL styles for consistent specificity. ([35771](https://github.com/WordPress/gutenberg/pull/35771))
 * Text: Fix text color value to use correct gray color value for Link UI preview
   description text. ([35851](https://github.com/WordPress/gutenberg/pull/35851))

#### Global Styles

 * Fix navigation in global styles 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.. ([36203](https://github.com/WordPress/gutenberg/pull/36203))
 * Fix presets data for themes that do not provide any preset. ([36054](https://github.com/WordPress/gutenberg/pull/36054))
 * Generate preset metadata for font-family in the site editor. ([36022](https://github.com/WordPress/gutenberg/pull/36022))
 * Hotfix for leftovers of `WP_Theme_JSON_Resolver::Get_merged_data`. ([36173](https://github.com/WordPress/gutenberg/pull/36173))
 * Lower the specificity of border & padding styles for the outline block style 
   in the button block. ([35968](https://github.com/WordPress/gutenberg/pull/35968))
 * Theme.json: Remove custom prefixes from properties that did not land in 5.8. (
   [34485](https://github.com/WordPress/gutenberg/pull/34485))
 * Fix Rest global styles controller accessing configuration that may not exist.(
   [36047](https://github.com/WordPress/gutenberg/pull/36047))

#### Block Editor

 * Allow moving metaboxes to previously empty area. ([25187](https://github.com/WordPress/gutenberg/pull/25187))
 * Change `console.error` to `console.warn` for enqueued styles in the editor. (
   [35914](https://github.com/WordPress/gutenberg/pull/35914))
 * Fix inserter with block pattern categories. ([36116](https://github.com/WordPress/gutenberg/pull/36116))
 * Fix navigation block link control zero value in it. ([36198](https://github.com/WordPress/gutenberg/pull/36198))
 * Fix the update of link and suggestions in LinkControl. ([32320](https://github.com/WordPress/gutenberg/pull/32320))
 * Make Link UI inactive if selection extends beyond format bounds or encounters
   new link. ([35946](https://github.com/WordPress/gutenberg/pull/35946))
 * Fix selection by holding shift key for nested blocks. ([35668](https://github.com/WordPress/gutenberg/pull/35668))
 * Fix shift+click on a child block with its parent selected. ([35988](https://github.com/WordPress/gutenberg/pull/35988))
 * Fix: Crash when resetting user color palette. ([36233](https://github.com/WordPress/gutenberg/pull/36233))
 * Fix: Show user colors on palette indicator. ([36232](https://github.com/WordPress/gutenberg/pull/36232))
 * Fix `getPxFromCssUnit` test stability and test that memoized function works correctly.(
   [35939](https://github.com/WordPress/gutenberg/pull/35939))
 * Link editing: Account for link anchor no longer being present when generating
   unique link instance key. ([36357](https://github.com/WordPress/gutenberg/pull/36357))
 * Preserve highlighted text selection when changing colors ([36263](https://github.com/WordPress/gutenberg/pull/36263))

#### Design Tools

 * Font Appearance: Improve consistency of label in Typography panel. ([35860](https://github.com/WordPress/gutenberg/pull/35860))
 * Font Family Support: Fix skip serialization check. ([36073](https://github.com/WordPress/gutenberg/pull/36073))
 * Navigation: Force text decoration styles on nav item in editor. ([35859](https://github.com/WordPress/gutenberg/pull/35859))

#### Template Editor

 * Clear selected block when clicking outside in the template part focus mode. (
   [35816](https://github.com/WordPress/gutenberg/pull/35816))
 * Templates: Only include templates for the current post types. ([35802](https://github.com/WordPress/gutenberg/pull/35802))

#### Core Data

 * Avoid showing deleted records in editor saving flow. ([36027](https://github.com/WordPress/gutenberg/pull/36027))
 * Fix getEntityRecords to ensure resolution on REST API failure. ([36353](https://github.com/WordPress/gutenberg/pull/36353))
 * Fix Core Data using hardcoded baseURL prefix for taxonomies and post types API
   requests. ([35850](https://github.com/WordPress/gutenberg/pull/35850))
 * Make `saveEditedEntityRecord` use the entity key when available. ([36212](https://github.com/WordPress/gutenberg/pull/36212))

#### Patterns

 * Update unsaved navigation block flow. ([35976](https://github.com/WordPress/gutenberg/pull/35976))

#### Full Site Editing

 * Add fallback handling for plugins or themes using the CustomizerCustomizer Tool
   built into WordPress core that hooks into most modern themes. You can use it 
   to preview and modify many of your site’s appearance settings.. ([35877](https://github.com/WordPress/gutenberg/pull/35877))
 * Fix missing `<MainDashboardButton>` slot fill in site editor. ([36369](https://github.com/WordPress/gutenberg/pull/36369))
 * Remove duplicate Editor menu item. ([36342](https://github.com/WordPress/gutenberg/pull/36342))
 * Theme resolver: Fix crash from calls to `undefined` functions. ([36248](https://github.com/WordPress/gutenberg/pull/36248))
 * Unhook `_block_template_render_title_tag` to prevent duplicate title tags from
   rendering. ([36133](https://github.com/WordPress/gutenberg/pull/36133))

#### Widgets Editor

 * Fix layout styles not applying in widgets customizer. ([35865](https://github.com/WordPress/gutenberg/pull/35865))

#### CSSCSS Cascading Style Sheets. & Styling

 * Editor defaults for themes with no editor styles and when user disables theme
   styles. ([35736](https://github.com/WordPress/gutenberg/pull/35736))

#### History

 * Support disabling autosave for native Unsupported Block Editor. ([35639](https://github.com/WordPress/gutenberg/pull/35639))

### Performance

#### List View

 * Fix pagedown/pageup and improve scrolling. ([36063](https://github.com/WordPress/gutenberg/pull/36063))
 * List View: Render a fixed number of items. ([35230](https://github.com/WordPress/gutenberg/pull/35230))

#### Block Editor

 * Improve opening of the block inserter via manual token-based analysis of reusable
   blocks. ([35763](https://github.com/WordPress/gutenberg/pull/35763))

#### Widgets Editor

 * List View: Avoid re-rendering all items on block focus. Enable persistent List
   View 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. ([35706](https://github.com/WordPress/gutenberg/pull/35706))

### Experiments

#### Block Library

 * Navigation Area block. ([36178](https://github.com/WordPress/gutenberg/pull/36178))

#### Full Site Editing

 * Always display Customizer menu item. ([36168](https://github.com/WordPress/gutenberg/pull/36168))
 * Revert “Always display Customizer menu item”. ([36189](https://github.com/WordPress/gutenberg/pull/36189))
 * Remove slug and status columns from templates list in Appearance > Templates.(
   [35996](https://github.com/WordPress/gutenberg/pull/35996))

#### REST API

#### Navigation Editor

 * Show a warning when trying to save unsupported blocks. ([35993](https://github.com/WordPress/gutenberg/pull/35993))

### Documentation

 * Added link to Ways to keep up with Gutenberg & Full Site Editing. ([36077](https://github.com/WordPress/gutenberg/pull/36077))

#### Handbook

 * Add Thunks Tutorial. ([36051](https://github.com/WordPress/gutenberg/pull/36051))
 * Add a more detailed guide for reactReact React is a JavaScript library that makes
   it easy to reason about, construct, and maintain stateless and stateful user 
   interfaces. [https://reactjs.org](https://reactjs.org/) native development. (
   [35529](https://github.com/WordPress/gutenberg/pull/35529))
 * Blocks: Add view script to block schema and documentation. ([36175](https://github.com/WordPress/gutenberg/pull/36175))
 * Blocks: Document changes to style and editorStyle in `block.json`. ([36218](https://github.com/WordPress/gutenberg/pull/36218))
 * Add Getting Started level for documentation. ([35891](https://github.com/WordPress/gutenberg/pull/35891))
 * Add section about using the schema during development. ([35835](https://github.com/WordPress/gutenberg/pull/35835))
 * Fix a small typo in the “Getting started” documentation. ([36109](https://github.com/WordPress/gutenberg/pull/36109))
 * Fix Typos in widgets/overview.md. ([36078](https://github.com/WordPress/gutenberg/pull/36078))
 * Fix wording in the Authoring Experience documentation. ([35969](https://github.com/WordPress/gutenberg/pull/35969))
 * Improve Getting Started landing page. ([35893](https://github.com/WordPress/gutenberg/pull/35893))
 * Release Docs: Remove consecutive RCs warning. ([35855](https://github.com/WordPress/gutenberg/pull/35855))
 * Theme.json: Fix typo. ([36139](https://github.com/WordPress/gutenberg/pull/36139))
 * Theme.json docs: Add missing settings & styles. ([36137](https://github.com/WordPress/gutenberg/pull/36137))
 * Tweak organization for getting-started documentation. ([34091](https://github.com/WordPress/gutenberg/pull/34091))
 * Update the recommendation for the cadence of npm releases. ([35925](https://github.com/WordPress/gutenberg/pull/35925))

#### Packages

 * Components: Update Components CONTRIBUTING.md indentation. ([35866](https://github.com/WordPress/gutenberg/pull/35866))
 * Create Block: Move create-block changelog entries back to Unreleased section.(
   [35886](https://github.com/WordPress/gutenberg/pull/35886))
 * DOM: Backtick added around `<textarea>` input tag in readme file. ([34813](https://github.com/WordPress/gutenberg/pull/34813))
 * Env: Update wordpress-develop example to clarify src/build location. ([35978](https://github.com/WordPress/gutenberg/pull/35978))
 * Rich Text: Add usage documentation for Rich Text package. ([35885](https://github.com/WordPress/gutenberg/pull/35885))
 * Schemas: Fix schema file URL. ([36157](https://github.com/WordPress/gutenberg/pull/36157))

### Code Quality

#### REST API

 * Add Theme’s base global styles endpoint. ([35985](https://github.com/WordPress/gutenberg/pull/35985))
 * Improvements for the global styles endpoint. ([36071](https://github.com/WordPress/gutenberg/pull/36071))
 * Remove “experimental” from URL details REST controller and promote to `v1` namespace.(
   [35915](https://github.com/WordPress/gutenberg/pull/35915))

#### Block Library

 * Heading: Auto-generated anchors hide implementation details. ([35747](https://github.com/WordPress/gutenberg/pull/35747))
 * Mark FSE blocks as non experimental. ([35979](https://github.com/WordPress/gutenberg/pull/35979))
 * Mark Post Comments as stable and Comments Query Loop as experimental. ([36132](https://github.com/WordPress/gutenberg/pull/36132))
 * Mark Post Navigation Link and Term Description blocks as stable. ([36163](https://github.com/WordPress/gutenberg/pull/36163))
 * Remove `post-` prefix from Comment Template inner blocks. ([36171](https://github.com/WordPress/gutenberg/pull/36171))

#### Global Styles

 * Linting: Fix WPCSWordPress Community Support A public benefit corporation and
   a subsidiary of the WordPress Foundation, [established](https://wordpressfoundation.org/news/2016/introducing-wordpress-community-support-a-public-benefit-subsidiary/)
   in 2016. lint errors in global styles. ([36058](https://github.com/WordPress/gutenberg/pull/36058))
 * Refactor theme.json migrations to be a single class. ([36182](https://github.com/WordPress/gutenberg/pull/36182))
 * Remove locations we do not translate from `theme-i18n.json`. ([35881](https://github.com/WordPress/gutenberg/pull/35881))
 * Update `theme.json` schema migrations. ([36154](https://github.com/WordPress/gutenberg/pull/36154))

#### Post Editor

 * Migrate to thunks. ([35720](https://github.com/WordPress/gutenberg/pull/35720))
 * Refactor FlatTermSelector into a functional component. ([33459](https://github.com/WordPress/gutenberg/pull/33459))
 * Remove GB prefixed functions from template part. ([36180](https://github.com/WordPress/gutenberg/pull/36180))
 * Translated site properties. ([36097](https://github.com/WordPress/gutenberg/pull/36097))

#### Components

 * ToolsPanel: Use Grid component to handle layout. ([35621](https://github.com/WordPress/gutenberg/pull/35621))
 * Update spacing in CircularOptionPicker. ([36014](https://github.com/WordPress/gutenberg/pull/36014))
 * Use small button on tools panel toggle. ([35935](https://github.com/WordPress/gutenberg/pull/35935))

#### Other Packages

 * Create Block: Add block.json schema to generated file. ([35843](https://github.com/WordPress/gutenberg/pull/35843))
 * Data: Rename types file from .d.ts to .ts. ([36062](https://github.com/WordPress/gutenberg/pull/36062))
 * Url: Move getStablePath function into the wordrpess/url package. ([35992](https://github.com/WordPress/gutenberg/pull/35992))
 * Schemas: Add schemas package. ([35998](https://github.com/WordPress/gutenberg/pull/35998))
 * Schemas: Theme.json – Add `title` to templateParts. ([36145](https://github.com/WordPress/gutenberg/pull/36145))

#### CSS & Styling

 * Remove 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. buttons block CSS property.(
   [33793](https://github.com/WordPress/gutenberg/pull/33793))

### Tools

#### PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory 󠀁[https://wordpress.org/plugins/](https://wordpress.org/plugins/)󠁿 or can be cost-based plugin from a third-party. and backporting to WordPress core

 * Updates `WP_Theme_JSON_Resolver` and tests to be equal to core. ([36223](https://github.com/WordPress/gutenberg/pull/36223))
 * Changes for FSE 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. in core.(
   [36201](https://github.com/WordPress/gutenberg/pull/36201))
 * Temporarily pin .wp-env.json to WP 5.8.1. ([36333](https://github.com/WordPress/gutenberg/pull/36333))

#### Testing

 * Add a method to disable auto-accepting dialogs. ([35828](https://github.com/WordPress/gutenberg/pull/35828))
 * Skip broken widgets test. ([36239](https://github.com/WordPress/gutenberg/pull/36239))
 * Skip flaky test for loading block stylesheets in 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..(
   [35961](https://github.com/WordPress/gutenberg/pull/35961))
 * Tests: Run block fixtures through KSES. ([35611](https://github.com/WordPress/gutenberg/pull/35611))
 * theme.json: Make sure tests are pure. ([36253](https://github.com/WordPress/gutenberg/pull/36253))
 * theme.json: Update test data. ([35883](https://github.com/WordPress/gutenberg/pull/35883))
 * Scripts: Increase timeout for end-to-end tests to 30 seconds. ([35983](https://github.com/WordPress/gutenberg/pull/35983))
 * Improve 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](https://make.wordpress.org/core/2021/page/7/?output_format=md#regression).
   coverage for REST API menus endpoints. ([36177](https://github.com/WordPress/gutenberg/pull/36177))
 * Update child theme.json merge test to match core. ([36329](https://github.com/WordPress/gutenberg/pull/36329))

#### Debugging

 * Wp-env: Disable Xdebug by default unless specified by user. ([34324](https://github.com/WordPress/gutenberg/pull/34324))

## Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~
36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative
of the average editing experience but is adequate for spotting variations in performance.

| Version | Time to Render First Block | KeyPress Event (typing) | 
| Gutenberg 11.9 | 5.58s | 40.22ms | 
| Gutenberg 11.8 | 5.53s | 38.89ms | 
| WordPress 5.8 | 5.86s | 47.3ms |

Thank you to [@critterverse](https://profiles.wordpress.org/critterverse/) for the
assets included in this post, [@priethor](https://profiles.wordpress.org/priethor/)
for coordinating the release process, [@ramonopoly](https://profiles.wordpress.org/ramonopoly/)
and [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/) for proofreading
the release notes, and [@glendaviesnz](https://profiles.wordpress.org/glendaviesnz/),
[@zieladam](https://profiles.wordpress.org/zieladam/), [@noisysocks](https://profiles.wordpress.org/noisysocks/),
[@mamaduka](https://profiles.wordpress.org/mamaduka/), and [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)
for assisting with troubleshooting and pushing the release to the plugin directory,
and to all those who contributed to this big release! 🎉

[#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/),
[#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/)

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
6:23 pm _on_ November 11, 2021     
Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/),
[core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)   

# 󠀁[CSS Chat Agenda: November 11, 2021](https://make.wordpress.org/core/2021/11/11/css-chat-agenda-november-11-2021/)󠁿

The next weekly CSSCSS Cascading Style Sheets. meeting is today [Thursday, November 11, 2021, 4:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+Core+CSS+Chat&iso=20211111T21&p1=1440&ah=1)
in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel in Making
WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).
If there are any other topics you’d like to discuss, please leave a comment on this
post.

## Meeting Agenda

 * Welcome ([21:00pm UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+Core+CSS+Chat&iso=20211111T21&p1=1440&ah=1))
 * Announcements & housekeeping
    - Discuss meeting time
 * CSS Custom Properties ([#49930](https://core.trac.wordpress.org/ticket/49930))
 * CSS Audit Improvements & other projects
 * Open floor / CSS link share

See you there!

 [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-css](https://make.wordpress.org/core/tag/core-css/)

 [  ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/)
6:17 pm _on_ November 11, 2021     
Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[CSS Chat Summary: 04 November 2021](https://make.wordpress.org/core/2021/11/11/css-chat-summary-04-november-2021/)󠁿

[The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1636059901086500).
[@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/)
wrote up these notes.

## Announcements & housekeeping

 * [@notlaura](https://profiles.wordpress.org/notlaura/) noted some recent facilitator
   problems and asked for ideas to improve the situation, suggesting:
    - Continue as we are, with the chance of missed meetings
    - Take a winter break
    - Change the meeting frequency
 * [@ryelle](https://profiles.wordpress.org/ryelle/) responded that the meeting 
   have been helpful to coordinate the custom properties project but maybe the time
   doesn’t work so well for people, plus the EU daylight savings time change may
   have caused some disruption

## CSSCSS Cascading Style Sheets. Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿)

 * [@ryelle](https://profiles.wordpress.org/ryelle/) reported that there are still
   some open PRs to review, and also possibly some files that need to be re-claimed.
   It also looks unlikely that we’ll make the deadline for 5.9
 * [@ryelle](https://profiles.wordpress.org/ryelle/) added that the [planning doc](https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit)
   has tasks for late September 2021 which she thinks are still valid. She hopes
   that we can get some momentum up for 6.0
 * [@notlaura](https://profiles.wordpress.org/notlaura/) agreed that aiming for 
   6.0, and perhaps revising the meeting time, could help pick up some momentum

Thanks everybody!

[#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/)

 [  ](https://profiles.wordpress.org/fabiankaegy/) [Fabian Kaegy](https://profiles.wordpress.org/fabiankaegy/)
1:27 pm _on_ November 11, 2021     
Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/),
[core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/),
[gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[Editor chat summary: Wednesday, 10 November 2021](https://make.wordpress.org/core/2021/11/11/editor-chat-summary-wednesday-10-november-2021/)󠁿

This post summarizes the latest weekly Editor meeting ([agenda](https://make.wordpress.org/core/2021/11/09/editor-chat-agenda-10-november-2021/),
[slack transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1636552799128800)),
held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
channel, on [Wednesday, November 10, 2021, 03:00 PM GMT+1.](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20211110T15&p1=187&ah=1)

## General 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/](https://wordpress.org/gutenberg/)󠁿 11.9

Gutenberg 11.9 RC4 was released earlier today and the goal is to publish the stable
release Thursday morning APAC time, which should be around the end of the day Wednesday
10th in North America.

See the note from [@andrewserong](https://profiles.wordpress.org/andrewserong/) 
in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1636525612114600).

### WordPress 5.9

[Planning Roundup](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/)

[Preliminary Roadmap](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/)
[Feature Go/No Results](https://make.wordpress.org/core/2021/10/15/wordpress-5-9-feature-go-no-go-october-14-2021/)

[@noisysocks](https://profiles.wordpress.org/noisysocks/) shared the following 5.9
related updates:

 * The coreCore Core is the set of software required to run WordPress. The Core 
   Development Team builds WordPress. patches have been merged for 5.9. Follow up
   work from this is ongoing.
 * Gutenberg needs to be updated to work with core `trunk`. There were CI test failures
   so we changed CI to run 5.8.2 as a temporary fix. [@danr](https://wordpress.slack.com/team/UBDRWLECC)
   is working on updating Gutenberg, but help is appreciated
 * Please add 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. label to
   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. fix PRs
 * Please pick up an issue or two from the Must Haves board. There’s a few things
   with no assignee

[@mkaz](https://profiles.wordpress.org/mkaz/) shared an update on documentation 
for 5.9:

I’ve created a new public GitHubGitHub GitHub is a website that offers online implementation
of git repositories that can easily be shared, copied and modified by other developers.
Public repositories are free to host, private repositories require a paid subscription.
GitHub introduced the concept of the ‘pull request’ where code changes done in branches
by contributors can be reviewed and discussed before being merged by the repository
owner. [https://github.com/](https://github.com/) project to track documentation
needs for the WP 5.9 release. You can access it at: [https://github.com/orgs/WordPress/projects/11](https://github.com/orgs/WordPress/projects/11)

Let me know if you have trouble accessing that link. GitHub project is a new tool
so I’m still getting familiar, but basically a spreadsheet connected to GitHub issues
and tickets.

I pulled in all tickets labeled “Needs 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.” so please if you’ve worked on a ticketticket Created for both bug reports
and feature development on the bug tracker. definitely take a look. I’ll reach out
and confirm assigned, the ones listed now were pulled in automatically.

The “Doc Type” label is a general categoryCategory The 'category' taxonomy lets 
you group posts / content together that share a common bond. Categories are pre-
defined and broad ranging. I made up for the items.

 * **Dev Note** is a specific post on Make Core for developers for any breaking 
   changes in a release.
 * **User Docs** is intended for user facing documentation of new features for non-
   developers. For example, how do I use Global Styles?
 * **Dev Docs** is a catch-all for all other developer documentation that isn’t 
   necessarily a specific Dev Note, for example “How do I create a blockBlock Block
   is the abstract term used to describe units of markup that, composed together,
   form the content or layout of a webpage using the WordPress editor. The idea 
   combines concepts of what in the past may have achieved with shortcodes, custom
   HTML, and embed discovery into a single consistent API and user experience. theme?”
   or 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. updates.

One thing to note, the tabs at the top are actually views, so entries are filtered
by the type. So if you switch to a “tab” and add an entry, it actually “disappears”
since it doesn’t have the correct type to be shown in that view. So adding items
is easiest in Overview (all items) and then enter the Doc Type.

## Updates on the key projects:

### Navigation Block & Navigation Editor

[@get_dave](https://profiles.wordpress.org/get_dave/) shared an update on the [GitHub Tracking issue](https://github.com/WordPress/gutenberg/issues/35521#issuecomment-964940536)

 * Work has continued on making Navigations reusable across a Site and between Themes.
 * A [Navigation Area block was added](https://github.com/WordPress/gutenberg/pull/36178)
   to facilitate the reuse of Navigations between Themes. You can now switch Themes
   and (if the target Theme is configured correctly) your Navigation will be preserved.
 * This works somewhat similarly to Menu Locations in classic Themes:
    - you add a Nav _Area_ block and configure it to be `Primary`, `Secondary` or`
      Tertiary`. These terms are provided by default and denote an approximate hierarchy
      of navigations on a site.
    - you then insert a Nav block _inside_ the Nav Area block. This can be used 
      to configure _presentational_ properties of a given Menu and is ideal for 
      Theme Developers. Note you do not need to add any nav _items_ at this point.
    - you then optionally add _items_ to your Navigation block.
    - when switching Theme, assuming the new Theme also has a Navigation Area block
      with a matching “area” (e.g. Primary, Secondary, Tertiary), then any nav items
      from matching Navigation Areas on your old Theme will automatically appear
      in the associated location in the new Theme.
    - the navigation -> area relationship is saved via site options is a format 
      of  `{ "primary": 794, "secondary": 112 }`where the keys are the navigation
      _areas_ and the values are the post IDs of [Navigation post types](https://github.com/WordPress/gutenberg/pull/35746).

 * Lots of great work behind the scenes work on the REST APIREST API The REST API
   is an acronym for the RESTful Application Program Interface (API) that uses HTTP
   requests to GET, PUT, POST and DELETE data. It is how the front end of an application(
   think “phone app” or “website”) can communicate with the data store (think “database”
   or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)
   which has allowed all of the above to progress.
 * Tweaks to the UIUI User interface and UXUX User experience of the block itself
   have been ongoing.

### Mobile

[@Antonis](https://profiles.wordpress.org/antonis/) Lilis

**Improvements and Fixes**

 * Fix on the synchronisation mechanism for serialising content from the editor 
   on Android
 * Added more Integration tests for Embed block
 * Disabled swipe gesture on BottomSheets to fix scroll-axis issue

**In Progress**

 * Finalising tweaks to the Embed block
 * Finalising GSS Font size, line height and selected text colours.

### Global Styles

[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)

 * The focus this week was porting all the infrastructure to the core (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. changes endpoints, etc) and that is done.

### Template editor

 * No updates were shared

### Patterns

[@paaljoachim](https://profiles.wordpress.org/paaljoachim/)

 * The [Browse Patterns in a Modal PR](https://github.com/WordPress/gutenberg/pull/35773)
   by [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) has been merged 
   and will be included in WordPress 5.9

## Task Coordination:

_Note: Anyone reading this summary outside of the meeting, please drop a comment
in the post summary, if you can/want to help with something._

[@joen](https://profiles.wordpress.org/joen/)

Always navigation. So much is in flux, but I’m looking at bugfixes related to justification,
theming, submenus and others. It would help me if [github.com/WordPress/gutenberg/pull/36298](http://github.com/WordPress/gutenberg/pull/36298)
could be approved soon.

[@mamaduka](https://profiles.wordpress.org/mamaduka/)

I’m primarily working on WP 5.9 Must-Haves, helping with reviews, and trying to 
fix bugs, now and then.

## Open Floor:

[@Louis](https://profiles.wordpress.org/louis/)

 * Raised the [GitHub Issue #35994](https://github.com/WordPress/gutenberg/issues/35994)
   about which templates appear under “Appearance” > “Templates”
    - The Ticket was added to the [5.9 Must Haves board in GitHub](https://github.com/WordPress/gutenberg/projects/62#card-72608966).

[#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/),
[#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/),
[#summary](https://make.wordpress.org/core/tag/summary/)

 [  ](https://profiles.wordpress.org/estelaris/) [Estela Rueda](https://profiles.wordpress.org/estelaris/)
9:48 pm _on_ November 10, 2021     
Tags: [core ( 743 )](https://make.wordpress.org/core/tag/core/)

# 󠀁[Dev Chat Summary November 10, 2021](https://make.wordpress.org/core/2021/11/10/dev-chat-summary-november-10-2021/)󠁿

[@francina](https://profiles.wordpress.org/francina/) led the weekly meeting at 
20:00 UTC. [Here is the meeting agenda](https://make.wordpress.org/core/2021/11/10/dev-chat-agenda-for-november-10-2021/).

[Link to this <dev-chat> in #core](https://wordpress.slack.com/archives/C02RQBWTW/p1636574419337300)
on Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

## Notable news and blogblog (versus network, site) posts

 * [5.8.2 is out](https://wordpress.org/news/2021/11/wordpress-5-8-2-security-and-maintenance-release/)
 * 5.9 is in the Feature Freeze phase, which means defect work only. No more enhancements
   or new features before 6.0 Alpha
 * Two 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. scrubs sessions left for this release
   [Bug Scrub Schedule for 5.9](https://make.wordpress.org/core/2021/10/18/bug-scrub-schedule-for-5-9/)
 * [A Week in Core – November 8, 2021](https://make.wordpress.org/core/2021/11/08/a-week-in-core-november-8-2021/)
 * [Default git branch for wordpress/wordpress-develop](https://make.wordpress.org/core/2021/11/10/default-git-branch-for-wordpress-wordpress-develop/)

## Components check-in and status updates

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

 * There are currently 203 tickets open in the 5.9 milestone. [https://core.trac.wordpress.org/tickets/major/workflow](https://core.trac.wordpress.org/tickets/major/workflow)
 * These need to be committed or punted by 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 next week, which is November 16. Some of them could still
   make it into 5.9 if people step up to do the work.

### Testing

 * Join the [testing session on 12 November ](https://make.wordpress.org/meetings)
   on the Slack [#core](https://make.wordpress.org/core/tag/core/) channel

### Build/Test Tools

 * Added missing `@covers` tags for PHPUnit tests. See ticketticket Created for 
   both bug reports and feature development on the bug tracker. [#39265](https://core.trac.wordpress.org/ticket/39265)
   for more details.

### General

 * Polyfills for some new PHPPHP The web scripting language in which WordPress is
   primarily architected. WordPress requires PHP 7.4 or higher functions are landing
   in core:
    - `str_ends_with()` and `str_starts_with()` (PHP 8.0+). See ticket [#54377](https://core.trac.wordpress.org/ticket/54377)
      for more details.
    - `str_contains()` (PHP 8.0+). See ticket [#49652](https://core.trac.wordpress.org/ticket/49652)
      for more details.
    - `array_key_first()` and `array_key_last()` (PHP 7.3+). See ticket [#45055](https://core.trac.wordpress.org/ticket/45055)
      for more details.

This lets pluginPlugin A plugin is a piece of software containing a group of functions
that can be added to a WordPress website. They can extend functionality or add new
features to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. and theme developers use these functions
safely on older PHP versions.

### I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see 󠀁[localization](https://make.wordpress.org/core/2021/page/7/?output_format=md#l10n)󠁿. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

Login and registration screens are getting a language switcher.  See ticket [#43700](https://core.trac.wordpress.org/ticket/43700)
for more details.

### Date/Time, Permalinks

No major news this week

### Help/About

Two issues have been committed, and a third is on the way.

### Adopt a component!

[@francina](https://profiles.wordpress.org/francina/) invited contributors to adopt
a component. Interested? [Learn all about it](https://make.wordpress.org/core/components/).
Got questions? Interested? Contact [@francina](https://profiles.wordpress.org/francina/)
and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/).

## Open floor

[@marybaum](https://profiles.wordpress.org/marybaum/), [@webcommsat](https://profiles.wordpress.org/webcommsat/)
and [@nalininonstopnewsuk](https://profiles.wordpress.org/nalininonstopnewsuk/) 
adopted the [Quick/bulk edit ](https://make.wordpress.org/core/components/editor/quick-bulk-edit/)
component.

[@costdev](https://profiles.wordpress.org/costdev/) invited contributors to discuss
[what is possible or not in the time leading to the feature freeze](https://core.trac.wordpress.org/ticket/54410).

[@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) reminded us that
Build/Test Tools are not bound to milestones. So discussion, patches and commits
can continue regardless of feature freeze.

[#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-9](https://make.wordpress.org/core/tag/5-9/),
[#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/)

# Post navigation

[← Older posts](https://make.wordpress.org/core/2021/page/8/?output_format=md)

[Newer posts →](https://make.wordpress.org/core/2021/page/6/?output_format=md)