Title: 2021 – Page 27 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/itsjusteileen/) [Eileen Violini](https://profiles.wordpress.org/itsjusteileen/)
11:49 am _on_ July 7, 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/)

# 󠀁[Editor chat summary: 30 June 2021](https://make.wordpress.org/core/2021/07/07/editor-chat-summary-30-june-2021/)󠁿

This post summarizes the weekly editor chat meeting ([agenda here](https://make.wordpress.org/core/2021/06/29/editor-chat-agenda-30-june-2021/))
held on [Wednesday, 30 June, 2021, 10:00 AM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210623T1400)
in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1625061844143300). Moderated
by [@itsjusteileen](https://profiles.wordpress.org/get_dave/profile/).

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

[Gutenberg 11. RC 1 ](https://github.com/WordPress/gutenberg/releases/tag/v11.0.0-rc.1)
released on 30 June. The link includes release notes.

## WordPress 5.8

The first [Release Candidate](https://wordpress.org/news/2021/06/wordpress-5-8-release-candidate/)
is available. A few quick things from this post:

 * Theme and plugin authors should test and update their readme file.
   For theme 
   authors, [@youknowriad](https://profiles.wordpress.org/youknowriad/) has a post
   on updating your theme for content width to [work with global styles and settings](https://make.wordpress.org/core/2021/06/29/on-layout-and-content-width-in-wordpress-5-8/).
 * For the ployglots out there, this release marks the Hard String Freeze for 5.8.
 * Everyone is needed for final testing!

This might also be a good time to mention deprecated [Block Editor API’s](https://make.wordpress.org/core/2021/06/29/block-editor-api-removals-58/).
See [@youknowriad](https://profiles.wordpress.org/youknowriad/) posts for more information.

View the complete [WordPress 5.8 development cycle](https://make.wordpress.org/core/5-8/).

## Key Project Updates

### Full Site Editing

The latest call for testing is out: [FSE Program Testing Call #8: Thrive with Theme.json](https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/).
As noted in the post, this round of testing targets developer-centric users in order
to bring high impact feedback for 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., a new tool
for extenders. Feedback is requested by 14 July.

### Widgets Editor

See the full 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.-
based [Widgets Editor dev note](https://make.wordpress.org/core/2021/06/29/block-based-widgets-editor-in-wordpress-5-8/)
for a overview description of the new feature.

### Mobile

[@mattchowning](https://profiles.wordpress.org/mattchowning/) provided the update.

**“Shipped”:**Enabled tests for the Cover Block

**Coming Soon:**

 * Gallery block refactor
 * Tooltips to help with Editor Onboarding
 * Block inserter search

**In Progress:**

 * Further Editor Onboarding improvements: a help section and a “new” badge for 
   new blocks
 * Adding new integration tests for mobile embed block
 * Global Style Support for colors

### Navigation Block

[@mkaz](https://profiles.wordpress.org/mkaz/) provided the update.

 * Working on the overlay background colors for responsive menu and dropdowns is
   close
 * fixing up the Navigation Editor screen and working on improving tests.

### **Global Styles**

[@nosolosw](https://profiles.wordpress.org/nosolosw/) provided the update.

The current focus is polishing the theme.json experience by finding and fixing bugs
that are back ported to the Betas/RCrelease candidate One of the final stages in
the version release cycle, this version signals the potential to be a final release
to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2021/page/27/?output_format=md#alpha-beta)..
Two things left are:

 * 5779 Extract strings provided via theme.json for 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/27/?output_format=md#l10n),
   [internationalization](https://make.wordpress.org/core/2021/page/27/?output_format=md#i18n).
   in translate.wordpress.orgWordPress.org The community site where WordPress code
   is created and shared by the users. This is where you can download the source
   code for WordPress core, plugins and themes as well as the central location for
   community conversations and organization. [https://wordpress.org/](https://wordpress.org/).
   This depends on a new wp-cliWP-CLI WP-CLI is the Command Line Interface for WordPress,
   used to do administrative and development tasks in a programmatic way. The project
   page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/)
   release that includes this PR and then updating the 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. infrastructure.
 * 53494 The global styles need to be enqueued in the footer for classic themes 
   that opt-in into per-block asset loading.

The 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. for theme.json was published.

## Task Coordination

[@Zeb](https://profiles.wordpress.org/zeb/) is looking for review on his TOC Block
PR after fixing the 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)
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. in the [Table of Contents block PR](https://github.com/WordPress/gutenberg/pull/29739).

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

Making a little progress on nav block menu item setup states, with a little summary
here. Otherwise making PRs for a variety of small issues, in fact some of them just
need your green checkmarks!

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

Mainly doing FSE Outreach Program wrangling in the form of [shipping the theme.json call for testing post](https://make.wordpress.org/test/2021/06/24/call-for-testing-thrive-with-theme-json/)
with two lovely collaborators (join in on the fun!) and a “How to Test FSE items
for 5.8” post shipping today. I plan to turn my attention towards user docs starting
at the end of this week through to the release to help out there alongside responding
to feedback that comes in. I also want to spend more time in the land of 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/)
triaging.
[@mamaduka](https://profiles.wordpress.org/mamaduka/)

 * Updated documentation for ServerSideRender package.
 * Added check to avoid applying layout configs twice with 5.8.
 * Worked on adding busy state to the template creation modal. I would love some:
   eyes: on this PR.
 * Pushed improved check for Image Block “switch to cover” action.
 * Testing issues and helping out with PR reviews.

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

In preparation for the next months after 5.8, we are refining the Site Editing scope,
closing issues that have been completed for the most part, and creating new overview
issues with the upcoming work.

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

I am a one person mechanical end to end test runner for the block based widgets 
editor

## Open Floor

### What’s the status of FSE in 5.8?

[@ironwiller](https://profiles.wordpress.org/ironwiller/) Will there going to be
a change at WP 5.8 and have an actual FSE or this one is an ongoing project till
the end of the year or even beyond?

[@mamaduka](https://profiles.wordpress.org/mamaduka/) Template Mode is on for themes
that provide theme.json` file or have special support flag.

[@annezazu](https://profiles.wordpress.org/annezazu/) You can think of full site
editing as a collection of features that brings the familiar experience of blocks
to all parts of your site. Because it’s a collection of features, it means there’s
the option to only release what’s stable and ready in a more gradual way rather 
than all at once! So… think of it less as an “on/off switch” approach for releasing
FSE and more as a steady drip of features being released. In terms of what’s coming,
check out this post or you can watch this recent video from another community member
that goes over the major features planned. While some items related to FSE are going
to be released, like Query Loop Block or Template Editing Mode for classic themes
that opt in, this work will be ongoing and is expected to continue beyond this year(
my best guess).

### Embeds in iFrames Issue

[@mrMark](https://profiles.wordpress.org/mrmark/) Bump to have Embeds looked at 
e.g. [this issue](https://github.com/WordPress/gutenberg/issues/28490). I added 
a comment on about embeds being cut off because the iframeiframe iFrame is an acronym
for an inline frame. An iFrame is used inside a webpage to load another HTML document
and render it. This HTML document may also contain JavaScript and/or CSS which is
loaded at the time when iframe tag is parsed by the user’s browser. isn’t expanding
for the content.

### Replace white screen on home page

[@colorful-tones](https://profiles.wordpress.org/colorful-tones/)
Is there a means
to refrain from seeing white screen on home page if a theme just has a theme.json
in it? I’ve tested with TwentySomething themes and does not seem to happen, therefore
wondering if there is a deprecation jig in place for TwentySomething themes only
to gracefully fail. Query Monitor shows wp-content/plugins/gutenberg/lib/template-
canvas.php being loaded as template on home page. This is with WP 5.8 RC1-51270 
and Gutenberg 10.9.1 active. It looks like an issue needs to be created for this
topic for general review.

[#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/)

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
6:20 pm _on_ July 6, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[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 July 7, 2021](https://make.wordpress.org/core/2021/07/06/dev-chat-agenda-for-july-7-2021/)󠁿

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

## Blogblog (versus network, site) Post Highlights

 * [WordPress 5.8 RC 1](https://wordpress.org/news/2021/06/wordpress-5-8-release-candidate/)
 * [WordPress 5.8 Field Guide](https://make.wordpress.org/core/2021/07/03/wordpress-5-8-field-guide/)
 * [A Week in Core – July 5, 2021](https://make.wordpress.org/core/2021/07/05/a-week-in-core-july-5-2021/)

## 󠀁[5.8 Schedule Review](https://make.wordpress.org/core/5-8/)󠁿

 * **RCrelease candidate One of the final stages in the version release cycle, this
   version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2021/page/27/?output_format=md#alpha-beta).
   1 released last week and RC 2 yesterday, now under [hard string freeze](https://make.wordpress.org/polyglots/handbook/glossary/#hard-freeze)**
 * _Working on Field GuideField guide The field guide is a type of blogpost published
   on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/).
   The field guide generally lists all the dev notes published during the beta cycle.
   This guide is linked in the about page of the corresponding version of WordPress,
   in the release post and in the HelpHub version page. email to 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./theme authors_
 * No further 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 scheduled, so please highlight
   issues of concern directly in [#core](https://make.wordpress.org/core/tag/core/)
 * RC 3 in 6 days on Tuesday, July 13th
 * 5.8 release in 13 days on Tuesday, July 20th

## Components check-in and status updates

 * 5.8 plans and help needed
 * 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-8](https://make.wordpress.org/core/tag/5-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/),
[#dev-chat](https://make.wordpress.org/core/tag/dev-chat/)

 [  ](https://profiles.wordpress.org/kjellr/) [Kjell Reigstad](https://profiles.wordpress.org/kjellr/)
3:41 pm _on_ July 6, 2021     
Tags: [make.wordpress.org/themes ( 26 )](https://make.wordpress.org/core/tag/make-wordpress-org-themes/),
[p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)   

# 󠀁[X-post: Block-based Themes Meeting Agenda: July 7, 2021](https://make.wordpress.org/core/2021/07/06/xpost-block-based-themes-meeting-agenda-july-7-2021/)󠁿

X-post from [+make.wordpress.org/themes](https://make.wordpress.org/themes/): [Block-based Themes Meeting Agenda: July 7, 2021](https://make.wordpress.org/themes/2021/07/06/block-based-themes-meeting-agenda-july-7-2021/)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
10:45 pm _on_ July 5, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)   

# 󠀁[A Week in Core – July 5, 2021](https://make.wordpress.org/core/2021/07/05/a-week-in-core-july-5-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 June 28 and 
July 5, 2021.

 * 64 commits
 * 52 contributors
 * 65 tickets created
 * 16 tickets reopened
 * 67 tickets closed

Please note that the WordPress Core team released [WordPress 5.8 RC 1](https://wordpress.org/news/2021/06/wordpress-5-8-release-candidate/)
last week. Everyone is welcome to help testing the next major releasemajor release
A release, identified by the first two numbers (3.6), which is the focus of a full
release cycle and feature development. WordPress uses decimaling count for major
release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.
of WordPress 🌟

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=07%2F05%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

### Build/Test Tools

 * Add the 5.8 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 the workflow for testing branches
 * Add the `artifacts` directory to `svn-ignore` and `.gitignore` – [#53549](https://core.trac.wordpress.org/ticket/53549)
 * Replace `assertInternalType()` usage in unit tests – [#53491](https://core.trac.wordpress.org/ticket/53491),
   [#46149](https://core.trac.wordpress.org/ticket/46149)
 * Revert [51259-51256,51265] – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Split packages and blocks to their webpack configs – [#53397](https://core.trac.wordpress.org/ticket/53397)

### Bundled Themes

 * Correct `@since` tags for blockBlock Block is the abstract term used to describe
   units of markup that, composed together, form the content or layout of a webpage
   using the WordPress editor. The idea combines concepts of what in the past may
   have achieved with shortcodes, custom HTML, and embed discovery into a single
   consistent API and user experience. patterns – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Remove mention of “FSE” in Core – [#53497](https://core.trac.wordpress.org/ticket/53497)
 * Twenty Seventeen: Avoid JSJS JavaScript, a web scripting language typically executed
   in the browser. Often used for advanced user interfaces and behaviors. errors
   when displaying legacy widgets – [#53512](https://core.trac.wordpress.org/ticket/53512)
 * Twenty Twenty-One: Add missing documentation for some filters – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Twenty Twenty-One: Ensure Duotone images are displayed correctly in Dark Mode–
   [#53531](https://core.trac.wordpress.org/ticket/53531)
 * Twenty Twenty-One: Ensure the dropdown arrow displays for `<select>` elements
   when focused – [#53560](https://core.trac.wordpress.org/ticket/53560)
 * Twenty Twenty-One: Improve documentation per the documentation standards: – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Twenty Twenty: Add missing documentation for some filters – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)

### Coding Standards

 * Add missing visibility keywords to `WP_Theme`, `WP_Theme_JSON`, and `WP_Theme_JSON_Resolver`
   tests – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Apply an alignment fix after `composer format` – [#53375](https://core.trac.wordpress.org/ticket/53375)
 * Remove redundant type casting to array in `WP_Query::get_posts()` – [#53359](https://core.trac.wordpress.org/ticket/53359)

### Documentation

 * Add `@since` tags for `WP_Theme` class properties – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Add `@ticket` references to some `WP_Theme_JSON` tests – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Add and correct examples of common names for various dynamic 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. – [#53581](https://core.trac.wordpress.org/ticket/53581)
 * Add missing `@since` tags for some 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/)
   methods added in 5.8 – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Add missing `@since` tags for some `WP_Theme_JSON` methods
 * Adjust `wp_dashboard_browser_nag()` DocBlockdocblock (phpdoc, xref, inline docs)
   per the documentation standards – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Correct `@see` references for hooks in the `get_option()` description – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Correct `@since` annotation for `WP_Block_Type->view_script` – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Correct description for the `$image` parameter of the `wp_save_image_file` 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)
 * Correct description for the `upgrader_pre_install` filter – [#53546](https://core.trac.wordpress.org/ticket/53546)
 * Correct documentation for `rest_{$post_type}_query` and `rest_{$taxonomy}_query`
   filters – [#53568](https://core.trac.wordpress.org/ticket/53568)
 * Corrections and improvements to types used in docblocks for symbols, properties,
   and filters – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Descriptive improvements and corrections for various docblocks – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Document common names for dynamic hooks relating to metadata – [#53581](https://core.trac.wordpress.org/ticket/53581)
 * Document the globals used in `WP_REST_Widget_Types_Controller` and `WP_REST_Widgets_Controller`–
   [#52628](https://core.trac.wordpress.org/ticket/52628), [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Document the globals used in some REST API methods – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Fix the documentation for the `$tests` parameter of the `site_status_tests` filter–
   [#53399](https://core.trac.wordpress.org/ticket/53399), #46573
 * Further Improve documentation for wp_should_load_separate_core_block_assets()–
   [#53505](https://core.trac.wordpress.org/ticket/53505)
 * Further type corrections and improvements for various docblocks – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Improve documentation for `wp_should_load_separate_core_block_assets()` – [#53505](https://core.trac.wordpress.org/ticket/53505)
 * Improve documentation for optional parameters in `WP_Theme_JSON_Resolver` methods
   per the documentation standards – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Improve documentation for optional parameters in `WP_Theme_JSON` methods per 
   the documentation standards – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * List the expected type first instead of `WP_Error` in some REST API methods added
   in 5.8 – [#52628](https://core.trac.wordpress.org/ticket/52628), [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Miscellaneous docblock improvements – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Miscellaneous formatting corrections for docblocks – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Remove an empty line between `@param` and `@return` tags in some newly added 
   REST API methods, per the documentation standards – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Undo the accidental revert of [[51299]](https://core.trac.wordpress.org/changeset/51299)
   made in [[51300]](https://core.trac.wordpress.org/changeset/51300) – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Update documentation for `WP_Widget_Block` per the documentation standards – 
   [#52628](https://core.trac.wordpress.org/ticket/52628), [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Update syntax for multi-line comments per the documentation standards – [#52628](https://core.trac.wordpress.org/ticket/52628),
   [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Update the IRCIRC Internet Relay Chat, a network where users can have conversations
   online. IRC channels are used widely by open source projects, and by WordPress.
   The primary WordPress channels are **#wordpress** and **#wordpress-dev**, on 
   irc.freenode.net. link from Freenode to Libera.chat – [#53590](https://core.trac.wordpress.org/ticket/53590)

### Editor

 * Ensure global styles are loaded in the footer when loading core assets individually–
   [#53494](https://core.trac.wordpress.org/ticket/53494)
 * Ensure the Query block pattern categoryCategory The 'category' taxonomy lets 
   you group posts / content together that share a common bond. Categories are pre-
   defined and broad ranging. is translatable – [#53577](https://core.trac.wordpress.org/ticket/53577)
 * Prevent block stylesheets from loading when they do not exist – [#53375](https://core.trac.wordpress.org/ticket/53375)
 * Remove the experimental `experimental-link-color` feature – [#53175](https://core.trac.wordpress.org/ticket/53175)
 * Include the latest fixes targetted for 5.8 RC1 – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Package updates including fixes 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/)
   for WordPress 5.8 RC1 – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Remove unnecessary function_exists check in get_the_block_template_html – [#53578](https://core.trac.wordpress.org/ticket/53578),
   [#53176](https://core.trac.wordpress.org/ticket/53176)

### Help/About

 * WordPress 5.8 About Page – [#52775](https://core.trac.wordpress.org/ticket/52775)

### Query

 * Check each post-type’s capabilitiescapability 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). when querying multiple post-types – [#48556](https://core.trac.wordpress.org/ticket/48556)

### REST API

 * Allow multiple widgets to be deleted in a single batch request – [#53557](https://core.trac.wordpress.org/ticket/53557)

### Script Loader

 * Add `file` block assets to the `svn-ignore` list – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Fix PHPPHP The web scripting language in which WordPress is primarily architected.
   WordPress requires PHP 7.4 or higher notice caused by the `viewScript` for the`
   core/file` block – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Revert [51267] – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Use the provided block version when registering styles – [#53507](https://core.trac.wordpress.org/ticket/53507)

### Security

 * Add 5.8 to the list of versions receiving security updates

### Site Health

 * Improve readability of site titles – [#53535](https://core.trac.wordpress.org/ticket/53535)

### Upgrade/Install

 * Notify users of deactivated plugins during upgrade – [#53432](https://core.trac.wordpress.org/ticket/53432)
 * Widgets REST API: Fix non-multi widgets not appearing in wp_inactive_widgets –
   [#53534](https://core.trac.wordpress.org/ticket/53534)

## Props

**Thanks to the 52 people who contributed to WordPress Core on Trac last week:**
[@desrosj](https://profiles.wordpress.org/desrosj/) (9), [@walbo](https://profiles.wordpress.org/walbo/)(
6), [@aristath](https://profiles.wordpress.org/aristath/) (5), [@jorbin](https://profiles.wordpress.org/jorbin/)(
5), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (4), [@audrasjb](https://profiles.wordpress.org/audrasjb/)(
3), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (3), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)(
3), [@gziolo](https://profiles.wordpress.org/gziolo/) (3), [@nosolosw](https://profiles.wordpress.org/nosolosw/)(
2), [@swissspidy](https://profiles.wordpress.org/swissspidy/) (2), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)(
2), [@zieladam](https://profiles.wordpress.org/zieladam/) (2), [@pbiron](https://profiles.wordpress.org/pbiron/)(
2), [@nalininonstopnewsuk](https://profiles.wordpress.org/nalininonstopnewsuk/) (
1), [@meher](https://profiles.wordpress.org/meher/) (1), [@yvettesonneveld](https://profiles.wordpress.org/yvettesonneveld/)(
1), [@femkreations](https://profiles.wordpress.org/femkreations/) (1), [@oglekler](https://profiles.wordpress.org/oglekler/)(
1), [@alanjacobmathew](https://profiles.wordpress.org/alanjacobmathew/) (1), [@milana_cap](https://profiles.wordpress.org/milana_cap/)(
1), [@courane01](https://profiles.wordpress.org/courane01/) (1), [@annezazu](https://profiles.wordpress.org/annezazu/)(
1), [@matveb](https://profiles.wordpress.org/matveb/) (1), [@shaunandrews](https://profiles.wordpress.org/shaunandrews/)(
1), [@javiarce](https://profiles.wordpress.org/javiarce/) (1), [@ryokuhi](https://profiles.wordpress.org/ryokuhi/)(
1), [@Jorbin](https://profiles.wordpress.org/jorbin/) (1), [@Clorith](https://profiles.wordpress.org/clorith/)(
1), [@Boniu91](https://profiles.wordpress.org/boniu91/) (1), [@ryelle](https://profiles.wordpress.org/ryelle/)(
1), [@empatogen](https://profiles.wordpress.org/empatogen/) (1), [@melchoyce](https://profiles.wordpress.org/melchoyce/)(
1), [@noisysocks](https://profiles.wordpress.org/noisysocks/) (1), [@pbearne](https://profiles.wordpress.org/pbearne/)(
1), [@jrf](https://profiles.wordpress.org/jrf/) (1), [@dd32](https://profiles.wordpress.org/dd32/)(
1), [@ilovecats7](https://profiles.wordpress.org/ilovecats7/) (1), [@mcsf](https://profiles.wordpress.org/mcsf/)(
1), [@poena](https://profiles.wordpress.org/poena/) (1), [@dlh](https://profiles.wordpress.org/dlh/)(
1), [@andraganescu](https://profiles.wordpress.org/andraganescu/) (1), [@marybaum](https://profiles.wordpress.org/marybaum/)(
1), [@leogermani](https://profiles.wordpress.org/leogermani/) (1), [@jeffpaul](https://profiles.wordpress.org/jeffpaul/)(
1), [@ipstenu](https://profiles.wordpress.org/ipstenu/) (1), [@azaozz](https://profiles.wordpress.org/azaozz/)(
1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@chanthaboune](https://profiles.wordpress.org/chanthaboune/)(
1), [@cbringmann](https://profiles.wordpress.org/cbringmann/) (1), [@webcommsat](https://profiles.wordpress.org/webcommsat/)(
1), and [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/) (
1).

**Congrats and welcome to our 5 new contributors of the week!** [@femkreations](https://profiles.wordpress.org/femkreations/),
[@courane01](https://profiles.wordpress.org/courane01/), [@javiarce](https://profiles.wordpress.org/javiarce/),
[@empatogen](https://profiles.wordpress.org/empatogen/), and [@ilovecats7](https://profiles.wordpress.org/ilovecats7/)
♥️

**Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
26), [@desrosj](https://profiles.wordpress.org/desrosj/) (20), [@johnbillion](https://profiles.wordpress.org/johnbillion/)(
8), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (3), [@jorbin](https://profiles.wordpress.org/jorbin/)(
2), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (2), [@ryelle](https://profiles.wordpress.org/ryelle/)(
1), [@clorith](https://profiles.wordpress.org/clorith/) (1), and [@noisysocks](https://profiles.wordpress.org/noisysocks/)(
1).

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

 [  ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)
11:11 am _on_ July 5, 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/),
[meetings ( 14 )](https://make.wordpress.org/core/tag/meetings/)   

# 󠀁[Editor Chat Agenda: 7 July 2021](https://make.wordpress.org/core/2021/07/05/editor-chat-agenda-7-july-2021/)󠁿

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

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, July 7, 2021, 04:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210707T16&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 11.0 RC](https://github.com/WordPress/gutenberg/releases/tag/v11.0.0-rc.1)
 * [WordPress 5.8](https://github.com/WordPress/gutenberg/projects/55) (Project 
   board)
 * [Monthly Plan for June 2021](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/)(
   July update will be added soon) and key project updates:
    - Global Styles.
 *  - 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. based 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.
    - Navigation Block & Navigation Editor.
    - Full Site Editing.
    - 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 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/), 
[#meetings](https://make.wordpress.org/core/tag/meetings/)

 [  ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/)
4:55 pm _on_ July 3, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[field guide ( 35 )](https://make.wordpress.org/core/tag/field-guide/)   

# 󠀁[WordPress 5.8 Field Guide](https://make.wordpress.org/core/2021/07/03/wordpress-5-8-field-guide/)󠁿

---

**_UPDATE on 12 July 2021_**: The [Miscellaneous block editor API additions in WordPress 5.8](https://make.wordpress.org/core/2021/07/12/miscellaneous-block-editor-api-additions-in-wordpress-5-8/)
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. was added to the BlockBlock Block is the abstract
term used to describe units of markup that, composed together, form the content 
or layout of a webpage using the WordPress editor. The idea combines concepts of
what in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience. Editor section.

---

Whether you are a WordPress website user, builder, or developer, WordPress 5.8 brings
exciting changes and a hint of even more goodies coming in WordPress 5.9. But we’re
getting ahead of ourselves; let us take a look at what to expect in when 5.8 is 
released.

The WordPress 5.8 release cycle is different from previous ones in several ways,
but the [release squad](https://make.wordpress.org/core/5-8/) navigates it with 
ease, even though not entirely without pressure. One of these differences is a decision
to include an unplanned [Beta 4](https://wordpress.org/news/2021/06/wordpress-5-8-beta-4/)
into the release cycle. This is not such a surprise, given that there are [96 enhancements and feature requests](https://core.trac.wordpress.org/query?status=closed&type=enhancement&type=feature+request&milestone=5.8&max=500&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority),
[170 bug fixes](https://core.trac.wordpress.org/query?status=closed&type=defect+(bug)&milestone=5.8&max=500&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority)
and [24 other blessed tasks](https://core.trac.wordpress.org/query?status=closed&type=task+(blessed)&milestone=5.8&max=500&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority),
which brings us to [290 Trac tickets in total](https://core.trac.wordpress.org/query?status=closed&milestone=5.8&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority).

In this Field GuideField guide The field guide is a type of blogpost published on
Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/).
The field guide generally lists all the dev notes published during the beta cycle.
This guide is linked in the about page of the corresponding version of WordPress,
in the release post and in the HelpHub version page., you will notice what is relevant
to you and your users among the many improvements coming in 5.8.

## Block Editor

The block editor moves onward with regular releases. 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/)
version 10.7 is bundled with WordPress 5.8; that totals eight Gutenberg releases(
versions [10.0](https://make.wordpress.org/core/2021/02/17/whats-new-in-gutenberg-10-0-february/),
[10.1](https://make.wordpress.org/core/2021/03/02/whats-new-in-gutenberg-10-1-3-march/),
[10.2](https://make.wordpress.org/core/2021/03/17/whats-new-in-gutenberg-10-2-17-march/),
[10.3](https://make.wordpress.org/core/2021/04/02/whats-new-in-gutenberg-10-3-31-march/),
[10.4](https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/),
[10.5](https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/),
[10.6](https://make.wordpress.org/core/2021/05/14/whats-new-in-gutenberg-10-6-12-may/),
and [10.7](https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/))
all merged into this WordPress release (as the [related Gutenberg handbook page](https://developer.wordpress.org/block-editor/contributors/versions-in-wordpress/)
makes clear)! Bug fixes and performance improvements from Gutenberg versions [10.8](https://make.wordpress.org/core/2021/06/10/whats-new-in-gutenberg-10-8-9-june/)
and [10.9](https://make.wordpress.org/core/2021/06/24/whats-new-in-gutenberg-10-9-23-june/)
are also part of 5.8.

The [WordPress 5.8 Beta 1 post](https://wordpress.org/news/2021/06/wordpress-5-8-beta-1/)
highlights a lot of the version’s new features and improvements:

 * New site editing blocks
 * The powerful query block
 * The block List view
 * Duotone image effects
 * Updates to existing blocks
 * Recommended patterns

As well, those recommendations integrate with the Pattern Directory on WordPress.
orgWordPress.org The community site where WordPress code is created and shared by
the users. This is where you can download the source code for WordPress core, plugins
and themes as well as the central location for community conversations and organization.
[https://wordpress.org/](https://wordpress.org/), template editor, `theme.json`,
and blocks in 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. areas among other changes.

In the block editor-related dev notesdev note Each important change in WordPress
Core is documented in a developers note, (usually called dev note). Good dev notes
generally include a description of the change, the decision that led to this change,
and a description of how developers are supposed to work with that change. Dev notes
are published on Make/Core blog during the beta phase of WordPress release cycle.
Publishing dev notes is particularly important when plugin/theme authors and WordPress
developers need to be aware of those changes.In general, all dev notes are compiled
into a Field Guide at the beginning of the release candidate phase. below are important
details on how `theme.json` delivers editor style control and associated Global 
Settings and Global Styles, plus:

 * Blocks in widget areas
 *  `block.json` as canonical way to register block styles
 * deprecation of filters and introduction of context-aware replacements
 * Removal of previously deprecated `EditorGlobalKeyboardShortcuts` component, `
   hasUploadPermissions` selector, and hidden Subheading block
 * The iframed template editor portion of Full Site Editing
 * Block-styles loading enhancements

> [Introducing theme.json in WordPress 5.8](https://make.wordpress.org/core/2021/06/25/introducing-theme-json-in-wordpress-5-8/)

> [On layout and content width in WordPress 5.8](https://make.wordpress.org/core/2021/06/29/on-layout-and-content-width-in-wordpress-5-8/)

> [Block-based Widgets Editor in WordPress 5.8](https://make.wordpress.org/core/2021/06/29/block-based-widgets-editor-in-wordpress-5-8/)

> [Block API Enhancements in WordPress 5.8](https://make.wordpress.org/core/2021/06/23/block-api-enhancements-in-wordpress-5-8/)

> [Miscellaneous block editor API additions in WordPress 5.8](https://make.wordpress.org/core/2021/07/12/miscellaneous-block-editor-api-additions-in-wordpress-5-8/)

> [Block Editor API Changes to Support Multiple Admin Screens in WP 5.8](https://make.wordpress.org/core/2021/06/16/block-editor-api-changes-to-support-multiple-admin-screens-in-wp-5-8/)

> [Various Block Editor API removals in WordPress 5.8](https://make.wordpress.org/core/2021/06/29/block-editor-api-removals-58/)

> [Introducing the template editor in WordPress 5.8](https://make.wordpress.org/core/2021/06/16/introducing-the-template-editor-in-wordpress-5-8/)

> [Blocks in an iframed (template) editor](https://make.wordpress.org/core/2021/06/29/blocks-in-an-iframed-template-editor/)

> [Block-styles loading enhancements in WordPress 5.8](https://make.wordpress.org/core/2021/07/01/block-styles-loading-enhancements-in-wordpress-5-8/)

## Media

Amongst [all Media changes](https://core.trac.wordpress.org/query?status=closed&component=Media&milestone=5.8&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority),
the highlight is support for the WebP image format. Accompanied by new `image_editor_output_format`
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. (see [#52867](https://core.trac.wordpress.org/ticket/52867)), it will set
foundation for a real performance boost. You will also notice some UIUI User interface
improvements, such as replacing infinite scroll with AJAX response ([#50105](https://core.trac.wordpress.org/ticket/50105)
and [#40330](https://core.trac.wordpress.org/ticket/40330)) and copy-link button
on media upload screen ([#51754](https://core.trac.wordpress.org/ticket/51754)).

> [WordPress 5.8 adds WebP support](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/)

## Plugins

[Changes in the Plugins component](https://core.trac.wordpress.org/query?status=closed&component=Plugins&milestone=5.8&group=component&col=id&col=summary&col=component&col=owner&col=type&col=priority&col=version&order=priority)
aim to make 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. developers lives easier. From better
docs search ([#50734](https://core.trac.wordpress.org/ticket/50734)) and standardizing
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. terminology ([#50531](https://core.trac.wordpress.org/ticket/50531))
to ability to mark plugins as unmanaged ([#32101](https://core.trac.wordpress.org/ticket/32101))
and avoid overwriting plugin files caused by update conflicts.

> [Introducing “Update URI” plugin header in WordPress 5.8](https://make.wordpress.org/core/2021/06/29/introducing-update-uri-plugin-header-in-wordpress-5-8/)

## 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/)󠁿

[REST API changes](https://core.trac.wordpress.org/query?component=REST+API&milestone=5.8&or&focuses=~rest-api&milestone=5.8&or&component=Application+Passwords&milestone=5.8&col=id&col=summary&col=owner&col=type&col=status&col=priority&col=version&order=priority+)
are mainly focused on Widgets and sidebars but there is also a new operator for 
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).
queries within post collections, support for the eagerly awaited `AND` comparison,
which allows posts meeting all passed criteria are matched ([#41287](https://core.trac.wordpress.org/ticket/41287)).

> [REST API Changes in WordPress 5.8](https://make.wordpress.org/core/2021/06/29/rest-api-changes-in-wordpress-5-8/)

## Site Health

Amongst the UI fixes, [Site Health changes](https://core.trac.wordpress.org/query?status=closed&component=Site+Health&milestone=5.8&group=component&col=id&col=summary&col=component&col=owner&col=type&col=priority&col=version&order=priority)
bring new actions for extending the navigation in the Site Health screen ([#47225](https://core.trac.wordpress.org/ticket/47225)).
You will also find new info provided by Site Health via a list of the supported 
file types for the active image editor ([#53022](https://core.trac.wordpress.org/ticket/53022)).

> [Extending the Site Health interface in WordPress 5.8](https://make.wordpress.org/core/2021/06/22/extending-the-site-health-interface-in-wordpress-5-8/)

## Themes

Across the [Themes changes](https://core.trac.wordpress.org/query?status=closed&component=Themes&milestone=5.8&or&component=Bundled+Theme&milestone=5.8&group=component&col=id&col=summary&col=component&col=owner&col=type&col=priority&col=version&order=priority)
you will find two new action hooks, `delete_theme` and `deleted_theme` ([#16401](https://core.trac.wordpress.org/ticket/16401)),
a few UI improvements such as clearly showing if a theme is a child themeChild theme
A Child Theme is a customized theme based upon a Parent Theme. It’s considered best
practice to create a child theme if you want to modify the CSS of your theme. [https://developer.wordpress.org/themes/advanced-topics/child-themes/](https://developer.wordpress.org/themes/advanced-topics/child-themes/)(
[#30240](https://core.trac.wordpress.org/ticket/30240)), update counter in adminadmin(
and super admin) menu item ([#43697](https://core.trac.wordpress.org/ticket/43697)),
and removal of “Featured” tab in Add Themes screen ([#49487](https://core.trac.wordpress.org/ticket/49487)).

Also, older bundled themes are refreshed with some really nice block patterns for
your pleasure and inspiration.

> [Bundled themes changes in WordPress 5.8](https://make.wordpress.org/core/2021/06/21/bundled-themes-changes-in-wordpress-5-8/)

## Other Developer Updates

There are even more goodies in 5.8! Read through the dev notes below to see details
on how Internet Explorer 11 support is being dropped as well as assorted changes
to the Bootstrap/Load, Build/Test Tools, Formatting, General, Media, Posts/Post 
Types, 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., Themes, and Users components.

Alongside the dev notes below, also worth noting is that work has continued during
the 5.8 release cycle to increase the compatibility with PHP8 and its new features.
Please continue to test your code against PHP8 as we all work towards raising the
entire WordPress ecosystem compatibility with PHP8, thank you!

> [Dropping support for Internet Explorer 11](https://wordpress.org/news/2021/05/dropping-support-for-internet-explorer-11/)

> [Bootstrap/Load Changes in 5.8](https://make.wordpress.org/core/2021/06/09/bootstrap-load-changes-in-5-8/)

> [Miscellaneous developer focused changes in WordPress 5.8](https://make.wordpress.org/core/2021/06/28/miscellaneous-developer-focused-changes-in-wordpress-5-8/)

> [WordPress and PHP 8.0](https://make.wordpress.org/core/2020/11/23/wordpress-and-php-8-0/)

## But Wait, There is More!

5.8 offers so much more! Over [170](https://core.trac.wordpress.org/query?status=closed&type=defect+(bug)&milestone=5.8&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority)
bugs, [96](https://core.trac.wordpress.org/query?status=closed&type=enhancement&type=feature+request&milestone=5.8&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority)
enhancements and feature requests, and [24](https://core.trac.wordpress.org/query?status=closed&type=task+(blessed)&milestone=5.8&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority)
blessed tasks have been [marked as fixed in WordPress 5.8](https://core.trac.wordpress.org/query?status=closed&milestone=5.8&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority).

Here are a few that haven’t been highlighted:

 * Build/Test Tools: Remove `@babel/polyfill` in favor of `core-js/stable`, requires
   explicit addition of `regenerator-runtime` as script dependency if IE11 support
   is still required ([#52941](https://core.trac.wordpress.org/ticket/52941)).
 * Bundled Theme: Add Block Patterns to Twenty Ten to Twenty Fifteen default themes(
   [#51107](https://core.trac.wordpress.org/ticket/51107), [#51106](https://core.trac.wordpress.org/ticket/51106),
   [#51105](https://core.trac.wordpress.org/ticket/51105), [#51104](https://core.trac.wordpress.org/ticket/51104),
   [#51103](https://core.trac.wordpress.org/ticket/51103), [#51102](https://core.trac.wordpress.org/ticket/51102)).
 * Comments: `comments_pagination_base` missing in `get_comment_reply_link()` function(
   [#51189](https://core.trac.wordpress.org/ticket/51189)).
 * Comments: Comments list’s link should point to an actual article ([#52353](https://core.trac.wordpress.org/ticket/52353)).
 * Embeds: Process embeds for block widgets ([#51566](https://core.trac.wordpress.org/ticket/51566)).
 * Emoji: Bump `Twemoji` from 13.0.1 to 13.1.0 ([#52852](https://core.trac.wordpress.org/ticket/52852)).
 * External Libraries: Bump `jQuery` from 3.5.1 to 3.6.0 ([#52707](https://core.trac.wordpress.org/ticket/52707)).
 * External Libraries: Bump `Moment.js` from 2.27.0 to 2.29.1 ([#52853](https://core.trac.wordpress.org/ticket/52853)).
 * External Libraries: Bump `Requests` from 1.7.0 to 1.8.1 ([#53101](https://core.trac.wordpress.org/ticket/53101)
   and [#53334](https://core.trac.wordpress.org/ticket/53334)).
 * External Libraries: Bump `Underscore` from 1.8.3 to 1.13.1 ([#45785](https://core.trac.wordpress.org/ticket/45785)).
 * Media: Remove infinite scrolling behavior from the Media grid ([#50105](https://core.trac.wordpress.org/ticket/50105)).
 * Media: Add a copy-link button at the media upload page ([#51754](https://core.trac.wordpress.org/ticket/51754)).
 * Menus: Add ability to delete multiple menu items ([#21603](https://core.trac.wordpress.org/ticket/21603)).
 * Revisions: a new dynamic filter to specify post type for number of revisions 
   to save, `wp_{$post->post_type}_revisions_to_keep` ([#51550](https://core.trac.wordpress.org/ticket/51550)).
 * Role/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).: `
   user_can()` changed for `exist` capability for anonymous users ([#52076](https://core.trac.wordpress.org/ticket/52076)).
 * Upgrade/Install: Remove parsing of `readme.txt` files from `validate_plugin_requirements()`(
   [#48520](https://core.trac.wordpress.org/ticket/48520)).
 * Upgrade/Install: Fatal error during update to 5.8 of a site with an active Gutenberg
   plugin (version less than 10.7) ([#53432](https://core.trac.wordpress.org/ticket/53432)).
 * Widgets: Make sure `WP_Widget` constructor creates a correct `classname` value
   for a namespaced widget class ([#44098](https://core.trac.wordpress.org/ticket/44098)).
 * And much, much more!

Please, test your code. Fixing issues that your code has with WordPress coreCore
Core is the set of software required to run WordPress. The Core Development Team
builds WordPress. helps you and millions of WordPress sites.

_**Props to [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) and [@desrosj](https://profiles.wordpress.org/desrosj/)
for contributing to this guide.**_

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#field-guide](https://make.wordpress.org/core/tag/field-guide/)

 [  ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/)
8:04 pm _on_ July 1, 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: July 1, 2021](https://make.wordpress.org/core/2021/07/01/css-chat-agenda-july-1-2021/)󠁿

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled
for Thursday July 1 at 21:00PM UTC.

The meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/)
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/).

 * **Housekeeping**
 * **Discussion: Custom Properties** ([#49930](https://core.trac.wordpress.org/ticket/49930))
   
   Continue discussing the workflow for adding Custom Properties to coreCore Core
   is the set of software required to run WordPress. The Core Development Team builds
   WordPress..

 * **Open Floor + CSS Link Share**

If there’s any topic you’d like to discuss, please leave a comment below!

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

 [  ](https://profiles.wordpress.org/aristath/) [Ari Stathopoulos](https://profiles.wordpress.org/aristath/)
9:36 am _on_ July 1, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[dev-notes ( 647 )](https://make.wordpress.org/core/tag/dev-notes/)   

# 󠀁[Block-styles loading enhancements in WordPress 5.8](https://make.wordpress.org/core/2021/07/01/block-styles-loading-enhancements-in-wordpress-5-8/)󠁿

WordPress 5.8 improves the way we load blockBlock Block is the abstract term used
to describe units of markup that, composed together, form the content or layout 
of a webpage using the WordPress editor. The idea combines concepts of what in the
past may have achieved with shortcodes, custom HTML, and embed discovery into a 
single consistent API and user experience.-styles by introducing 2 new features:

 * Load styles only for rendered blocks in a page
 * Inline small styles

## Only load styles for used blocks

This is an opt-in, non-breaking change. Using the `should_load_separate_core_block_assets`
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., developers can opt-in to this feature:

    ```notranslate
    add_filter( 'should_load_separate_core_block_assets', '__return_true' );
    ```

Prior to WordPress 5.8, styles for all blocks were included in a `style.css` file
that gets loaded on every page. By opting-in to separate styles loading, the following
will happen:

 * The `wp-block-library` stylesheet changes: Instead of loading the `wp-includes/
   css/dist/block-library/style.css` file which contains all styles for all blocks,
   this handle will now load the (much smaller) `wp-includes/css/dist/block-library/
   common.css` file, which contains generic styles like the default colors definitions,
   basic styles for text alignments, and styles for the `.screen-reader-text` class.
 * Styles for blocks will only get enqueued when the block gets rendered on a page.

The above changes will only apply to the frontend of a site, so all editor styles
will continue to work as they did before.

### The difference between block themes and classic themes

#### Block themes

In a block theme, blocks get parsed before the `<head>` so we always know which 
blocks will be present prior to rendering a page. This makes it possible to add 
the block styles to the `<head>` of our document.

#### Classic themes

In a classic, php-based theme, when a page starts to render, WordPress is not aware
which blocks exist on a page and which don’t. Blocks gets parsed on render, and 
what that means is that block-styles don’t get added in the `<head>` of the page.
Instead, they are added to the footer, when [`print_late_styles()`](https://developer.wordpress.org/reference/functions/print_late_styles/)
runs.

If you have an existing theme and you want to opt-in to this improvement, you will
need to test your theme for style priorities. Opting-in to separate styles loading
in a classic theme means that the loading order of styles changes. Block styles 
that used to be in the head will move to the footer, so you will need to check your
theme’s styles and make sure any opinionated styles you add to blocks have a higher
priority than coreCore Core is the set of software required to run WordPress. The
Core Development Team builds WordPress. styles.

### Taking advantage of separate styles loading to add 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./theme styles to blocks

It is possible to use this new feature to attach styles to existing block-styles,
by inlining them.

If your theme adds styles to blocks, instead of loading a single file containing
all styles for all blocks, you can split styles and have a single file per-block.
This will allow you to only load your theme’s (or plugin’s) block styles only when
a block exists on a page.

The function below is an example implementation of how to do that, with some additional
tweaks:

 * It works both in WordPress 5.8 and previous versions
 * It has a fallback in case the `should_load_separate_core_block_assets` filter
   is disabled
 * It adds styles both in the editor and frontend
 * Checks for specific editor block styles.

Feel free to use this as an example, tweaking it to suit your needs and implementation.

    ```notranslate
    /**
     * Attach extra styles to multiple blocks.
     */
    function my_theme_enqueue_block_styles() {
    	// An array of blocks.
    	$styled_blocks = [ 'paragraph', 'code', 'cover', 'group' ];

    	foreach ( $styled_blocks as $block_name ) {
    		// Get the stylesheet handle. This is backwards-compatible and checks the
    		// availability of the `wp_should_load_separate_core_block_assets` function,
    		// and whether we want to load separate styles per-block or not.
    		$handle = (
    			function_exists( 'wp_should_load_separate_core_block_assets' ) &&
    			wp_should_load_separate_core_block_assets()
    		) ? "wp-block-$block_name" : 'wp-block-library';

    		// Get the styles.
    		$styles = file_get_contents( get_theme_file_path( "styles/blocks/$block_name.min.css" ) );

    		// Add frontend styles.
    		wp_add_inline_style( $handle, $styles );

    		// Add editor styles.
    		add_editor_style( "styles/blocks/$block_name.min.css" );
    		if ( file_exists( get_theme_file_path( "styles/blocks/$block_name-editor.min.css" ) ) ) {
    			add_editor_style( "styles/blocks/$block_name-editor.min.css" );
    		}
    	}
    }
    // Add frontend styles.
    add_action( 'wp_enqueue_scripts', 'my_theme_enqueue_block_styles' );
    // Add editor styles.
    add_action( 'admin_init', 'my_theme_enqueue_block_styles' );
    ```

## Inlining small assets

In some cases small stylesheets get loaded on WordPress sites. These stylesheets
require the browser to make an additional request to get an asset, and while they
benefit from caching, their small size doesn’t justify that extra request, and performance
would improve if they were inlined.

To that end, an inlining mechanism was implemented. This is an opt-in feature, and
can be handled on a per-stylesheet basis. Internally, only assets that have data
for `path` defined get processed, so to opt-in, a stylesheet can add something like
this:

    ```notranslate
    wp_style_add_data( $style_handle, 'path', $file_path );
    ```

When a page gets rendered, stylesheets that have opted-in to get inlined get added
to an array. Their size is retrieved using a `filesize` call (which is why the `
path` data is necessary), and the array is then ordered by ascending size (smaller
to larger stylesheet). We then start inlining these assets by going from smallest
to largest, until a 20kb limit is reached.

A filter is available to change that limit to another value, and can also be used
to completely disable inlining.

To completely disable small styles inlining:

    ```notranslate
    add_filter( 'styles_inline_size_limit', '__return_zero' );
    ```

To change the total inlined styles limit to 50kb:

    ```notranslate
    add_filter( 'styles_inline_size_limit', function() {
    	return 50000; // Size in bytes.
    });
    ```

Inlining these styles happens by changing the `src` of the style to `false`, and
then adding its contents as inline data. This way we avoid backwards-compatibility
issues in themes and any additional styles attached to these stylesheets using `
wp_add_inline_style` will still be printed.

Please note that if a stylesheet opts-in to get inlined, that is no guarantee that
it will get inlined.

If for example on a page there are 30 stylesheets that are 1kb each, and they all
opt-in to be inlined, then only 20 of them will be converted from `<link rel="stylesheet"/
>` to `<style>` elements. When the 20th stylesheet gets inlined the 20kb limit is
reached and the inlining process stops. The remaining 10 stylesheets will continue
functioning like before and remain `<link>` elements.

If your theme opts-in to the separate block-styles, core block styles by default
have `path` defined so they can all be inlined.

Props [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) for proofreading
this dev-note.

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/)

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
9:29 pm _on_ June 29, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/)

# 󠀁[Dev Chat Summary: June 23, 2021](https://make.wordpress.org/core/2021/06/29/dev-chat-summary-june-23-2021/)󠁿

Chats were led by [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)
and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/). Opened with intros and
welcome.

## Highlighted Posts

 * Dev notesdev note Each important change in WordPress Core is documented in a 
   developers note, (usually called dev note). Good dev notes generally include 
   a description of the change, the decision that led to this change, and a description
   of how developers are supposed to work with that change. Dev notes are published
   on Make/Core blog during the beta phase of WordPress release cycle. Publishing
   dev notes is particularly important when plugin/theme authors and WordPress developers
   need to be aware of those changes.In general, all dev notes are compiled into
   a Field Guide at the beginning of the release candidate phase. are shipping!
 * BlockBlock Block is the abstract term used to describe units of markup that, 
   composed together, form the content or layout of a webpage using the WordPress
   editor. The idea combines concepts of what in the past may have achieved with
   shortcodes, custom HTML, and embed discovery into a single consistent API and
   user experience. Editor 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 to Support Multiple Adminadmin(
   and super admin) Screens in WP 5.8
 * Bundled themes changes in WordPress 5.8
 * Extending the Site Health interface in WordPress 5.8
 * Block API Enhancements in WordPress 5.8
 * Meeting notes and stuff
 * Regular posts on A Week in CoreCore Core is the set of software required to run
   WordPress. The Core Development Team builds WordPress. plus CSSCSS Cascading 
   Style Sheets. and Editor chat summaries are also available to peruse.

## WP5.8 Things

 * Test the beta! https://wordpress.org/news/2021/06/wordpress-5-8-beta-3/
 * We added a 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.!
   Beta 4 is Thursday
 * RC1 is next Tuesday
 * Call for help! https://core.trac.wordpress.org/tickets/major/workflow everything
   in the Has Patch/Needs Testing and Needs Patch sections could use input. 

## Component Check-in

 * **Build/Test Tools**: sourceMaps are now ignored for non WordPress Core files
   to avoid a build failure for custom plugins or themes located in build/wp-content.
   See ticketticket Created for both bug reports and feature development on the 
   bug tracker. [#52689](https://core.trac.wordpress.org/ticket/52689) for more 
   details.
 * **GitGit Git is a free and open source distributed version control system designed
   to handle everything from small to very large projects with speed and efficiency.
   Git is easy to learn and has a tiny footprint with lightning fast performance.
   Most modern plugin and theme development is being done with this version control
   system. [https://git-scm.com/](https://git-scm.com/)** is now used when fetching
   the WordPress Importer for unit tests. Previously, SVNSVN Subversion, the popular
   version control system (VCS) by the Apache project, used by WordPress to manage
   changes to its codebase. was used and the commands were not correctly run within
   the Docker container. See ticket [#52909](https://core.trac.wordpress.org/ticket/52909)
   for more details.
 * **Bundled themes**: There are a few tickets related to polishing the new blocks
   added in 5.8 that need testing. And the default themes also need more testing
   in general for 5.8. If that’s within your area of expertise, please feel free
   to help out with that.

## Open Floor

 * Request for feedback on https://core.trac.wordpress.org/ticket/53450 ([additional context in the original comment](https://make.wordpress.org/core/2021/06/22/dev-chat-agenda-for-june-23-2021/#comment-41433))
 * theme.json testing program is open: https://make.wordpress.org/test/2021/06/24/
   call-for-testing-thrive-with-theme-json/
 * FSE Outreach schedule is posted: https://make.wordpress.org/test/2021/06/09/upcoming-
   fse-outreach-program-schedule-june-july/

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

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
9:19 pm _on_ June 29, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)   

# 󠀁[A Week in Core – June 28, 2021](https://make.wordpress.org/core/2021/06/29/a-week-in-core-june-28-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 June 21 and 
June 28, 2021.

 * 60 commits
 * 64 contributors
 * 79 tickets created
 * 8 tickets reopened
 * 78 tickets closed

Please note that the WordPress Core team released [WordPress 5.8 beta 3](https://wordpress.org/news/2021/06/wordpress-5-8-beta-3/)
and [beta 4](https://wordpress.org/news/2021/06/wordpress-5-8-beta-4/) last week.
Everyone is welcome to help testing the next major releasemajor release A release,
identified by the first two numbers (3.6), which is the focus of a full release 
cycle and feature development. WordPress uses decimaling count for major release
versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress
🌟

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=06%2F28%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

### Build/Test tools

 * Add the `regenerator-runtime` script as a dependency to `wp-polyfill` – [#52941](https://core.trac.wordpress.org/ticket/52941)
 * Correct PHPUnit version requirement in tests using `::createPartialMock()` – 
   [#52625](https://core.trac.wordpress.org/ticket/52625)
 * Replace `assertEquals()` with `assertSameSets()` in text 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. tests – [#52482](https://core.trac.wordpress.org/ticket/52482),
   [#52625](https://core.trac.wordpress.org/ticket/52625)
 * Require PHPUnit >= 6 in tests using `::createPartialMock()` – [#52625](https://core.trac.wordpress.org/ticket/52625)
 * Use `assertSame()` in `_wp_to_kebab_case()` tests – [#52482](https://core.trac.wordpress.org/ticket/52482),
   [#52625](https://core.trac.wordpress.org/ticket/52625), [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Use more appropriate assertions in a few tests – [#52625](https://core.trac.wordpress.org/ticket/52625)

### Bundled Themes

 * Improve display of blocks in widget areas – [#53422](https://core.trac.wordpress.org/ticket/53422)
 * Improve 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/)
   check before activating an FSE theme – [#53410](https://core.trac.wordpress.org/ticket/53410)
 * Prevent a Full Site Editing theme from being activated when Gutenberg is not 
   active – [#53410](https://core.trac.wordpress.org/ticket/53410)
 * Remove mention of “FSE” in Core – [#53497](https://core.trac.wordpress.org/ticket/53497)
 * Remove unexpected border around the Theme Details button – [#53473](https://core.trac.wordpress.org/ticket/53473)
 * Twenty Nineteen: Update margins on full- and wide-aligned blocks in the editor–
   [#53428](https://core.trac.wordpress.org/ticket/53428)
 * Twenty Thirteen: Improve the display of 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)
   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. – [#53438](https://core.trac.wordpress.org/ticket/53438)
 * Twenty Twenty-One: Add margins around content in Post Template block – [#53389](https://core.trac.wordpress.org/ticket/53389),
   [#53398](https://core.trac.wordpress.org/ticket/53398)
 * Twenty Twenty-One: Add spacing around Query block when there is a background 
   color – [#53398](https://core.trac.wordpress.org/ticket/53398)
 * Twenty Twenty-One: Use the theme version when enqueueing theme assets – [#53502](https://core.trac.wordpress.org/ticket/53502)
 * Twenty Twenty: Remove extra margin within the Query Loop block – [#53482](https://core.trac.wordpress.org/ticket/53482)

### Coding standards

 * Apply an alignment fix from running `composer format` – [#53481](https://core.trac.wordpress.org/ticket/53481)
 * 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. issues in [[51227]](https://core.trac.wordpress.org/changeset/51227)–
   [#53475](https://core.trac.wordpress.org/ticket/53475)
 * Use a consistent check for parent items in `WP_Walker` – [#53474](https://core.trac.wordpress.org/ticket/53474)

### Docs

 * Document `api_version` and `variations` properties in `WP_Block_Type::__construct()`–
   [#53518](https://core.trac.wordpress.org/ticket/53518)
 * Fix typo in `widgets-block-editor` feature documentation – [#53424](https://core.trac.wordpress.org/ticket/53424)
 * Remove inaccurate `@since` 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.) – [#53461](https://core.trac.wordpress.org/ticket/53461),
   [#50105](https://core.trac.wordpress.org/ticket/50105)
 * Shorten the copyright notice for the `WP_REST_Sidebars_Controller` class – [#41683](https://core.trac.wordpress.org/ticket/41683)
 * Update documentation for `WP_Widget_Block` per the documentation standards – 
   [#52628](https://core.trac.wordpress.org/ticket/52628), [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Various docblockdocblock (phpdoc, xref, inline docs) corrections for code added
   in 5.8 – [#53461](https://core.trac.wordpress.org/ticket/53461)
 * Various 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. docblock improvements – [#52920](https://core.trac.wordpress.org/ticket/52920)

### Editor

 * Allow `custom-units` to be an array – [#53472](https://core.trac.wordpress.org/ticket/53472)
 * Correct variable names in `get_block_editor_settings()` – [#53458](https://core.trac.wordpress.org/ticket/53458)
 * Ports 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 for betaBeta A 
   pre-release of software that is given out to a large group of users to trial 
   under real conditions. Beta versions have gone through alpha testing in-house
   and are generally fairly close in look, feel and function to the final product;
   however, design changes often occur as part of the process. 3 – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Do not load a default font family for themes with theme.json
 * Move caching to endpoint for unique responses – [#53435](https://core.trac.wordpress.org/ticket/53435)
 * Package updates for Beta 3 – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Package updates including fixes from Gutenberg for WordPress 5.8 RC1 – [#53397](https://core.trac.wordpress.org/ticket/53397)
 * Remove empty `blocks/query-loop` directory – [#52991](https://core.trac.wordpress.org/ticket/52991)
 * Send localeLocale A locale is a combination of language and regional dialect.
   Usually locales correspond to countries, as is the case with Portuguese (Portugal)
   and Portuguese (Brazil). Other examples of locales include Canadian English and
   U.S. English., version with remote pattern requests – [#53435](https://core.trac.wordpress.org/ticket/53435)
 * Update the packages with a number of fixes targeted for Beta 4 – [#53397](https://core.trac.wordpress.org/ticket/53397)

### General

 * Ensure `svn:eol-style` is consistently set for all recently added files – [#53528](https://core.trac.wordpress.org/ticket/53528)

### Media

 * Add lazy-loading support to block-based widgets – [#53463](https://core.trac.wordpress.org/ticket/53463),
   [#53464](https://core.trac.wordpress.org/ticket/53464)
 * Correct undefined variable in wp_ajax_query_attachments – [#50105](https://core.trac.wordpress.org/ticket/50105)
 * Improve upload page media item layout on smaller screens – [#51754](https://core.trac.wordpress.org/ticket/51754)
 * Prevent uploading and show an error message when the server doesn’t support editing
   of WebP files and image sub-sizes cannot be created – [#53475](https://core.trac.wordpress.org/ticket/53475)
 * Prevent uploading and show an error message when the server doesn’t support editing
   of WebP images, take II. Add new, better error message for it – [#53475](https://core.trac.wordpress.org/ticket/53475)
 * Revert [r51211](https://core.trac.wordpress.org/changeset/51211) to restore `
   ms-files.php` assets – [#53492](https://core.trac.wordpress.org/ticket/53492),
   [#53475](https://core.trac.wordpress.org/ticket/53475)

### 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/)󠁿

 * Include the 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. ID when saving a widget – [#53452](https://core.trac.wordpress.org/ticket/53452)
 * Retrieve latest widgets before loading sidebars – [#53489](https://core.trac.wordpress.org/ticket/53489)

### Site Health

 * Add a unique wrapper for dashboard widget content – [#53521](https://core.trac.wordpress.org/ticket/53521)

### Widgets

 * Fix non-multi widgets not appearing in wp_inactive_widgets – [#53534](https://core.trac.wordpress.org/ticket/53534)
 * Add editor styles to the widgets block editor – [#53344](https://core.trac.wordpress.org/ticket/53344).–
   [#53388](https://core.trac.wordpress.org/ticket/53388)
 * Add missing `label` and `description` to 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. controls – [#53487](https://core.trac.wordpress.org/ticket/53487)
 * Add support for the Widgets Editor on `after_setup_theme` instead of `widgets_init`–
   [#53424](https://core.trac.wordpress.org/ticket/53424)
 * Avoid a TypeError when adding a widget in the Customizer – [#53488](https://core.trac.wordpress.org/ticket/53488),
   [#53421](https://core.trac.wordpress.org/ticket/53421), [#53419](https://core.trac.wordpress.org/ticket/53419)
 * Fix an “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. value” warning when
   adding a new widget in the Customizer – [#53479](https://core.trac.wordpress.org/ticket/53479)
 * Fix widget preview not working if widget registered via a instance
 * Remove unnecessary gutenberg_ functions – [#53441](https://core.trac.wordpress.org/ticket/53441)
 * Stop loading `wp-editor` and the Block Directory assets on the widgets screen–
   [#53437](https://core.trac.wordpress.org/ticket/53437), [#53397](https://core.trac.wordpress.org/ticket/53397)

## Props

**Thanks to the 64 people who contributed to WordPress Core on Trac last week:**
[@noisysocks](https://profiles.wordpress.org/noisysocks/) (10), [@desrosj](https://profiles.wordpress.org/desrosj/)(
9), [@ryelle](https://profiles.wordpress.org/ryelle/) (7), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)(
5), [@nosolosw](https://profiles.wordpress.org/nosolosw/) (4), [@zieladam](https://profiles.wordpress.org/zieladam/)(
4), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (4), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/)(
4), [@aristath](https://profiles.wordpress.org/aristath/) (3), [@scruffian](https://profiles.wordpress.org/scruffian/)(
3), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (3), [@azaozz](https://profiles.wordpress.org/azaozz/)(
3), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (3), [@gziolo](https://profiles.wordpress.org/gziolo/)(
3), [@johnbillion](https://profiles.wordpress.org/johnbillion/) (3), [@walbo](https://profiles.wordpress.org/walbo/)(
3), [@caseymilne](https://profiles.wordpress.org/caseymilne/) (3), [@youknowriad](https://profiles.wordpress.org/youknowriad/)(
2), [@jorbin](https://profiles.wordpress.org/jorbin/) (2), [@Mamaduka](https://profiles.wordpress.org/mamaduka/)(
2), [@dd32](https://profiles.wordpress.org/dd32/) (2), [@joedolson](https://profiles.wordpress.org/joedolson/)(
2), [@kevin940726](https://profiles.wordpress.org/kevin940726/) (2), [@jamesros161](https://profiles.wordpress.org/jamesros161/)(
2), [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) (2), [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/)(
2), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) (2), [@marybaum](https://profiles.wordpress.org/marybaum/)(
1), [@ocean90](https://profiles.wordpress.org/ocean90/) (1), [@daisyo](https://profiles.wordpress.org/daisyo/)(
1), [@tellyworth](https://profiles.wordpress.org/tellyworth/) (1), [@sumaiyasiddika](https://profiles.wordpress.org/sumaiyasiddika/)(
1), [@danieldudzic](https://profiles.wordpress.org/danieldudzic/) (1), [@mkaz](https://profiles.wordpress.org/mkaz/)(
1), [@Presskopp](https://profiles.wordpress.org/presskopp/) (1), [@joen](https://profiles.wordpress.org/joen/)(
1), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) (1), [@andraganescu](https://profiles.wordpress.org/andraganescu/)(
1), [@sunxiyuan](https://profiles.wordpress.org/sunxiyuan/) (1), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)(
1), [@kraftner](https://profiles.wordpress.org/kraftner/) (1), [@onemaggie](https://profiles.wordpress.org/onemaggie/)(
1), [@jffng](https://profiles.wordpress.org/jffng/) (1), [@otto42](https://profiles.wordpress.org/otto42/)(
1), [@Boniu91](https://profiles.wordpress.org/boniu91/) (1), [@Clorith](https://profiles.wordpress.org/clorith/)(
1), [@alanjacobmathew](https://profiles.wordpress.org/alanjacobmathew/) (1), [@mbabker](https://profiles.wordpress.org/mbabker/)(
1), [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) (1), [@strategio](https://profiles.wordpress.org/strategio/)(
1), [@poena](https://profiles.wordpress.org/poena/) (1), [@naoki0h](https://profiles.wordpress.org/naoki0h/)(
1), [@ixkaito](https://profiles.wordpress.org/ixkaito/) (1), [@antpb](https://profiles.wordpress.org/antpb/)(
1), [@aleperez92](https://profiles.wordpress.org/aleperez92/) (1), [@iandunn](https://profiles.wordpress.org/iandunn/)(
1), [@barry](https://profiles.wordpress.org/barry/) (1), [@mukesh27](https://profiles.wordpress.org/mukesh27/)(
1), [@herregroen](https://profiles.wordpress.org/herregroen/) (1), [@jeherve](https://profiles.wordpress.org/jeherve/)(
1), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (1), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)(
1), [@cbringmann](https://profiles.wordpress.org/cbringmann/) (1), and [@AlePerez92](https://profiles.wordpress.org/aleperez92/)(
1).

**Congrats and welcome to our 3 new contributors of the week!** [@sumaiyasiddika](https://profiles.wordpress.org/sumaiyasiddika/),
[@sunxiyuan](https://profiles.wordpress.org/sunxiyuan/), and [@alanjacobmathew](https://profiles.wordpress.org/alanjacobmathew/)
♥️

**Core committers:** [@desrosj](https://profiles.wordpress.org/desrosj/) (24), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
11), [@ryelle](https://profiles.wordpress.org/ryelle/) (4), [@youknowriad](https://profiles.wordpress.org/youknowriad/)(
3), [@noisysocks](https://profiles.wordpress.org/noisysocks/) (3), [@iandunn](https://profiles.wordpress.org/iandunn/)(
3), [@jorbin](https://profiles.wordpress.org/jorbin/) (2), [@azaozz](https://profiles.wordpress.org/azaozz/)(
2), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) (2), [@clorith](https://profiles.wordpress.org/clorith/)(
1), [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/) (1),
[@joedolson](https://profiles.wordpress.org/joedolson/) (1), [@flixos90](https://profiles.wordpress.org/flixos90/)(
1), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (1), and [@antpb](https://profiles.wordpress.org/antpb/)(
1).

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

# Post navigation

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

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