Title: 2021 – Page 40 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/peterwilsoncc/) [Peter Wilson](https://profiles.wordpress.org/peterwilsoncc/)
2:47 am _on_ April 28, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/)

# 󠀁[Dev Chat Agenda for April 28, 2021](https://make.wordpress.org/core/2021/04/28/dev-chat-agenda-for-april-28-2021/)󠁿

Here is the agenda for this week’s developer meetings to occur at the following 
times: [April 28, 2021 at 5:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210428T0500)
and [April 28 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210428T2000).

## Blogblog (versus network, site) Post Highlights

 * [A Week in Core – April 26, 2021](https://make.wordpress.org/core/2021/04/26/a-week-in-core-april-26-2021/)
 * [Core Editor Improvement: Refining the Block Toolbar](https://make.wordpress.org/core/2021/04/23/core-editor-improvement-refining-the-block-toolbar/)
 * [WP5.8 Squad Call for Volunteers](https://make.wordpress.org/core/2021/04/23/wp5-8-squad-call-for-volunteers/)—
   [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) will be working
   to finalize the squad in the coming days
 * [IE 11 Support Phase Out Plan](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/)
 * [Upcoming Full Site Editing Outreach Program Schedule](https://make.wordpress.org/test/2021/04/22/upcoming-fse-outreach-program-schedule/)
 * [Curious About Full Site Editing?](https://wordpress.org/news/2021/04/curious-about-full-site-editing/)

## Blog posts that need feedback

 * [Automatically Catching Bugs in Plugins](https://make.wordpress.org/meta/2021/04/27/automatically-catching-bugs-in-plugins/)

## Components check-in and status updates

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

## Open Floor

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

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

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

[#5-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/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
11:58 pm _on_ April 27, 2021     
Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/),
[5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[DevChat meeting Summary – April 21, 2021](https://make.wordpress.org/core/2021/04/27/devchat-meeting-summary-april-21-2021/)󠁿

[@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/)
led the weekly meetings of the WordPress CoreCore Core is the set of software required
to run WordPress. The Core Development Team builds WordPress. team, respectively
at 05:00 UTC and 20:00 UTC. Here is the [meeting agenda](https://make.wordpress.org/core/2021/04/20/dev-chat-agenda-for-april-21-2021/).

[Link to 05:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1618981248414400)

[Link to 20:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1619035213470700)

## Release announcements

### WordPress 5.7.1

[WordPress 5.7.1 was released](https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/)
on Wednesday April 14, 2021. This security and maintenance release features 26 bugbug
A bug is an error or unexpected result. Performance improvements, code optimization,
and are considered enhancements, not defects. After feature freeze, only bugs are
dealt with, with regressions (adverse changes from the previous version) being the
highest priority. fixes in addition to two security fixes.

There are only 6 tickets in the next milestone (5.7.2), and as for now there is 
no urgent thing to address.

### WordPress 5.8

Some blogblog (versus network, site) posts were published on Make/Core:

 * [Gutenberg 10.4 has been released](https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/)
 * [Full Site Editing Go/No Go | April 14, 2021](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/)
 * [Full Site Editing Go/No Go: Next steps](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)

[@annezazu](https://profiles.wordpress.org/annezazu/) shared that 2 weeks are left
to go on a [Query Quest](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/)
and give feedback. Worth noting there is also [an Italian version of the testing process](https://it.wordpress.org/team/2021/04/21/chiamata-per-il-test-del-programma-fse-5-alla-ricerca-delle-query/)(
props to [@piermario](https://profiles.wordpress.org/piermario/)). If you have issues
with the call for testing or questions about setting up a test site, please feel
free to ask [@annezazu](https://profiles.wordpress.org/annezazu/) in the [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
channel on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

[@chanthaboune](https://profiles.wordpress.org/chanthaboune/) shared that the next
step for WP 5.8 is to get a release team together.

While she’s finally not available to lead the release squad, [@francina](https://profiles.wordpress.org/francina/)
will be available to help wrangling contributors and mentoring. She will also publish
a call for release team members on Make/Core.

## Make/Core News

 * [A Week in Core – April 12, 2021](https://make.wordpress.org/core/2021/04/12/a-week-in-core-april-12-2021/)
   
   Thanks to the 22 people who contributed to WordPress Core on TracTrac An open
   source project by Edgewall Software that serves as a bug tracker and project 
   management tool for WordPress. last week!
 * [What’s next in Gutenberg? (April 2021)](https://make.wordpress.org/core/2021/04/08/whats-next-in-gutenberg-april-2021/)
 * [Recent Build/Test Tool changes and GitHub Actions update](https://make.wordpress.org/core/2021/04/08/recent-build-test-tool-changes-and-github-actions-update/)

## Blog posts that need feedback: FLoC concerns

One blogpost was discussed during most of the meeting time:

 * [Proposal: Treat FLoC like a security concern](https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/)

[@carike](https://profiles.wordpress.org/carike/) posted the proposal, and an active
discussion started with more than 100 commenters. For those interested, there is
a [summary of the discussion on WP Tavern](https://wptavern.com/wordpress-contributors-propose-blocking-floc-in-core).
Worth also noting that [@helen](https://profiles.wordpress.org/helen/), lead developer
of the project, published a [top comment about the proposal](https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/#comment-41139).

[@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) previously shared
[a comment from the Security team in the initial post](https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/#comment-41168):**
based on the information presented, this should not be considered a security issuesecurity
issue A security issue is a type of bug that can affect the security of WordPress
installations. Specifically, it is a report of a bug that you have found in the 
WordPress core code, and that you have determined can be used to gain some level
of access to a site running WordPress that you should not have. at this time.**

Worth noting that 3 people from Google Chrome DevRel team attended the meeting: 
[@michaelkleber](https://profiles.wordpress.org/michaelkleber/) as Chrome Tech Lead
for the ads-related APIs, [@r0wan](https://profiles.wordpress.org/r0wan/) and [@samdutton](https://profiles.wordpress.org/samdutton/)
as Chrome DevRel.

**Below you’ll find some direct quotes from [this open floor discussion](https://wordpress.slack.com/archives/C02RQBWTW/p1619036348023000):**

[@michaelkleber](https://profiles.wordpress.org/michaelkleber/) shared that the 
FLoC initiative is just at the beginning of what Chrome calls an Origin Trial — 
that’s the way we introduce new proposed APIs to get feedback from developers.

[@joyously](https://profiles.wordpress.org/joyously/) asked whether FLoC simply 
is a cookie of another flavor or not.
[@r0wan](https://profiles.wordpress.org/r0wan/)
answered there is a key difference with a cookie is that it’s a _1:1_ token the 
server sets on the client. With the FLoC id, it’s a _1:many_ grouping that does 
not enable that same direct link back to an individual across different sites. It’s
also not a value that the server gets to set for the client.[@michaelkleber](https://profiles.wordpress.org/michaelkleber/)
added that the key contrast with third-party cookies is that a FLoC cohort can’t
be used to know information specifically about _you_. Instead it allows some kind
of probabilistic information about a large group of people that you’re temporarily
part of (each FLoC cohort has thousands of people in it).

[@carike](https://profiles.wordpress.org/carike/) shared with [a detailed use case](https://wordpress.slack.com/archives/C02RQBWTW/p1619036685042700)
and asked for the safeguards that are in place to prevent this.

[@helen](https://profiles.wordpress.org/helen/)’s asked what is the utility is of
disabling FLoC on the content provider front vs. on the consumer front.
[@michaelkleber](https://profiles.wordpress.org/michaelkleber/)
answered that in the final end state, they expect the way FLoC will work is that
the only pages that will be relevant to calculating your cohort are the pages that
call the FLoC 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..  So pages will “opt in” by using some new JSJS JavaScript, a web 
scripting language typically executed in the browser. Often used for advanced user
interfaces and behaviors. function call. The HTTPHTTP HTTP is an acronym for Hyper
Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web
and this protocol defines how messages are formatted and transmitted, and what actions
Web servers and browsers should take in response to various commands. headerHeader
The header of your site is typically the first thing people will experience. The
masthead or header art located across the top of your page is part of the look and
feel of your website. It can influence a visitor’s opinion about your content and
you/ your organization’s brand. It may also look different on different screen sizes.
being discussed here was introduced as a way that pages could include random 3rd-
party JS without worrying that it would invoke that API without them expecting it.
So the HTTP header is saying “There is a new API that exists in the web, and I want
to be sure my page _cannot_ use it”.

[@michaelkleber](https://profiles.wordpress.org/michaelkleber/): FLoC doesn’t involve
saving any new information, it’s just calculated based on the recent browsing history—
and not the full URLURL A specific web address of a website or web page on the Internet,
such as a website’s URL www.wordpress.org even, just the domain name.

[@helen](https://profiles.wordpress.org/helen/): So on its own by default, a WordPress-
served page of content is not going to be used to calculate. However, if you were
to, say, embed something that includes a piece of JS, that JS could then call the
API and it would include the entire page?
[@r0wan](https://profiles.wordpress.org/r0wan/)
answered: so a default WordPress page with no use of the FLoC JS API and no ad-tagged
resources in it will not be used as part of the FLoC calculations. If that site 
includes a third-party that uses FLoC then that would include the top-level page.

[@michaelkleber](https://profiles.wordpress.org/michaelkleber/): There is a bunch
of on-device clustering that goes into making sure that your FLoC is shared with
thousands of other people. If you want to read more about the technical details 
of clustering, [here’s the page that describes it all](https://www.chromium.org/Home/chromium-privacy/privacy-sandbox/floc).

[@macmanx](https://profiles.wordpress.org/macmanx/): So, is there’s no point in 
a site blocking FLoC if that site is not using FLoC-enabled resources? If a site
were not using AdSense, it’s most likely not even going to be included in FLoC? 
And, on the other hand, if that site were already running AdSense, it probably benefits
from FLoC and would not want to 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.?

[@samdutton](https://profiles.wordpress.org/samdutton/) nodded: During the current
FLoC origin trial, a page visit will only be included in the browser’s FLoC computation
for one of two reasons:

 * The FLoC API `document.interestCohort()` is used on the page;
 * Chrome detects that the page [loads ads or ads-related resources](https://github.com/WICG/floc/issues/82).

[@macmanx](https://profiles.wordpress.org/macmanx/): So, FLoC only triggers when
resources that benefit (or are assumed to benefit) from FLoC are present. If I have
that right, then WordPress blocking FLoC software-wide would be similar to blocking
Google Fonts software-wide. It would have an _effect_ but would actually be more
of a negative impact to the site itself.

[@michaelkleber](https://profiles.wordpress.org/michaelkleber/): We’re running the
Origin Trial so that we can get feedback, and what we hear from people (including
you, now) is the kind of feedback that affects the end decision.
So it seems to 
me that this group is generally in favor of our best-guess plan (only look at pages
that actually invoke the FLoC API), for which thank you. But I’m sure we’ll hear
other opinions as well.

[@mkaz](https://profiles.wordpress.org/mkaz/): I think debating the merits of FLoC
is a bit beyond the point, it may or may not be evil, probably no more or less than
say AdSense. Where we wouldn’t introduce something to WordPress that would explicitly
block a site from implementing AdSense, right?
[@carike](https://profiles.wordpress.org/carike/):
The proposal just changes it from opt-out to opt-in. It does not prohibit someone
from opting in.[@westonruter](https://profiles.wordpress.org/westonruter/): If the
page has to opt-in to FLoC by using an API then what’s the point of also requiring
the site to opt-in to allowing FLoC as well? Going back to the Google Fonts example,
if WordPress blocked Google Fonts from being used except if an opt-in is used, then
if a theme enqueued a Google Font stylesheet then they’d _also_ have to add the 
code to opt-in to not blocking Google Fonts. That doesn’t make sense to me. It’s
like requiring a double opt-in?[@mkaz](https://profiles.wordpress.org/mkaz/): It
doesn’t seem like the area of the WordPress software to automatically opt people
out of something in their browser.

[@helen](https://profiles.wordpress.org/helen/): So, a user/consumer disabling FLoC
in their browser would mean they are not dropped into a bucket that’s used to determine
ads/whatever that they see around the web (or… wherever). A WordPress site by default
will not be used as a part of determining a given user’s bucket.
[@macmanx](https://profiles.wordpress.org/macmanx/):
It seems to me, based on all this discussion, the best place for anti-FLoC measures
are in the browser under control of the viewer, not in the site. If a site is triggering
FLoC in the first place, it likely intends to benefit from FLoC in some way.

[@carike](https://profiles.wordpress.org/carike/) shared a quote from the Chromium
repository: _“Any request made within an ad 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. is considered
an ad resource request.”_
[@michaelkleber](https://profiles.wordpress.org/michaelkleber/):
The point is that Chrome’s Ad Tagging is trying to figure out exactly which _resources_
are ads — very important if you want to, for example, unload ads that use too many
bytes.  So the rule is “anything loaded inside an ad counts as part of the ad”. 
But for FLoC, we’re asking a much coarser question: “Does this page have any ad 
stuff on it at all?”  So details about which specific items are part of that ad 
are irrelevant.

[@jorbin](https://profiles.wordpress.org/jorbin/): In my personal opinion, WordPress
is best off making a decision of no action at this time (not that we are making 
a decision in the meeting). FLoC as of right now is in such a small trial that we
as a project should continue to monitor it and try to encourage that the final implementation
is one that is going to align with us a project, but as of now it doesn’t present
any danger to individuals on the web and in fact has the potential to benefit many
publishers.

At the end of the chat, [@jorbin](https://profiles.wordpress.org/jorbin/) shared
a reminder about the [Post & Comment Guidelines on Make/Core blogs](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/)
to everyone that has posting abilities on make/core that we do have a page with 
expectations for posting there and that 1) All posts should be peer reviewed (it
currently states by a committercommitter A developer with commit access. WordPress
has five lead developers and four permanent core developers with commit access. 
Additionally, the project usually has a few guest or component committers - a developer
receiving commit access, generally for a single release cycle (sometimes renewed)
and/or for a specific component., but I personally would say project leaders who
are not committer would fall into that bucket) and 2) That the peer reviewer should
be recognized in the post.

The Google Chrome DevRel Team members shared that everyone is welcome to get in 
touch them via the [chromiumDev Twitter account](https://twitter.com/chromiumdev)
or the [FLoC repository on GitHub](https://github.com/WICG/floc).

After the devchat, [@helen](https://profiles.wordpress.org/helen/) opened a ticketticket
Created for both bug reports and feature development on the bug tracker. to summarize
the discussion and to discuss the next steps: **[#53069: Consider implications of FLoC and any actions to be taken on the provider (WordPress) front](https://core.trac.wordpress.org/ticket/53069)**.
Everyone is welcome to contribute to the discussion in this Trac ticket.

_Thanks [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) for the quick
review._

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

 [  ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/)
4:50 pm _on_ April 27, 2021     
Tags: [make.wordpress.org/meta ( 8 )](https://make.wordpress.org/core/tag/make-wordpress-org-meta/),
[p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)   

# 󠀁[X-post: Automatically Catching Bugs in Plugins](https://make.wordpress.org/core/2021/04/27/xpost-automatically-catching-bugs-in-plugins/)󠁿

X-post from [+make.wordpress.org/meta](https://make.wordpress.org/meta/): [Automatically Catching Bugs in Plugins](https://make.wordpress.org/meta/2021/04/27/automatically-catching-bugs-in-plugins/)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
9:57 pm _on_ April 26, 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 – April 26, 2021](https://make.wordpress.org/core/2021/04/26/a-week-in-core-april-26-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 April 19 and
April 26, 2021.

 * 20 commits
 * 27 contributors
 * 38 tickets created
 * 2 tickets reopened
 * 31 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker.
numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=04%2F26%2F2021&daysback=7&authors=&ticket=on&sfp_email=&sfph_mail=&update=Update).
The following is a summary of commits, organized by component.

## Code changes

### Bootstrap/Load

 * Add Function for reliable timing data – [#39163](https://core.trac.wordpress.org/ticket/39163)
 * Improve `get_bookmark()` test coverage – [#52988](https://core.trac.wordpress.org/ticket/52988)
 * Remove Internet Explorer 11 from the `browserslist` – [#53077](https://core.trac.wordpress.org/ticket/53077)
 * Update the `caniuse-lite` database – [#52624](https://core.trac.wordpress.org/ticket/52624)
 * Update several dependencies – [#52624](https://core.trac.wordpress.org/ticket/52624)
 * Add seeking support to stream test library – [#52922](https://core.trac.wordpress.org/ticket/52922),
   [#52826](https://core.trac.wordpress.org/ticket/52826)

### Coding Standards

 * Remove loose comparison in `wp-admin/includes/plugin-install.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/update-core.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/class-wp-terms-list-table.php` – 
   [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Fix minor, inline spacing issue in `wp-admin/setup-config.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)

### Code Modernization

 * Bring consistency to preparing some fields on Networknetwork (versus site, blog)
   Settings screen: – [#51423](https://core.trac.wordpress.org/ticket/51423)

### Documentation

 * Add a `@since` note to `wp_mail()` about using `is_email()` for validation – 
   [#52628](https://core.trac.wordpress.org/ticket/52628)

### Editor

 * Shape 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 filters to work better with the GutenbergGutenberg The
   Gutenberg project is the new Editor Interface for WordPress. The editor improves
   the process and experience of creating new content, making writing rich content
   much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
   HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   pluginPlugin A plugin is a piece of software containing a group of functions 
   that can be added to a WordPress website. They can extend functionality or add
   new features to your WordPress websites. WordPress plugins are written in the
   PHP programming language and integrate seamlessly with WordPress. These can be
   free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. – [#52920](https://core.trac.wordpress.org/ticket/52920)
 * Abstract block editor configuration – [#52920](https://core.trac.wordpress.org/ticket/52920)

### External Libraries

 * Update Underscore to version 1.13.1 – [#45785](https://core.trac.wordpress.org/ticket/45785)
 * Update `Moment.js` to the latest version – [#52853](https://core.trac.wordpress.org/ticket/52853)

### Plugins

 * When loading a plugin in a “sandbox” on activation, do it once – [#31104](https://core.trac.wordpress.org/ticket/31104)
 * When loading a plugin in a “sandbox” on activation, do it in a separate function–
   [#31104](https://core.trac.wordpress.org/ticket/31104)

### Posts, Post Types

 * Pass the post object to `the_password_form` 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. – [#29008](https://core.trac.wordpress.org/ticket/29008)

### Upgrade/Install

 * Prevent possible type errors during installation – [#51423](https://core.trac.wordpress.org/ticket/51423)

### Users

 * Share current user instance across functions – [#28020](https://core.trac.wordpress.org/ticket/28020)

## Props

**Thanks to the 27 people who contributed to WordPress Core on Trac last week:**

[@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (3), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)(
3), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (2), [@jrf](https://profiles.wordpress.org/jrf/)(
2), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (2), [@hareesh-pillai](https://profiles.wordpress.org/hareesh-pillai/)(
2), [@matt](https://profiles.wordpress.org/matt/) (1), [@xknown](https://profiles.wordpress.org/xknown/)(
1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@nosolosw](https://profiles.wordpress.org/nosolosw/)(
1), [@jeremyfelt](https://profiles.wordpress.org/jeremyfelt/) (1), [@andraganescu](https://profiles.wordpress.org/andraganescu/)(
1), [@azaozz](https://profiles.wordpress.org/azaozz/) (1), [@jorbin](https://profiles.wordpress.org/jorbin/)(
1), [@silb3r](https://profiles.wordpress.org/silb3r/) (1), [@andy](https://profiles.wordpress.org/andy/)(
1), [@chaion07](https://profiles.wordpress.org/chaion07/) (1), [@mensmaximus](https://profiles.wordpress.org/mensmaximus/)(
1), [@DrewAPicture](https://profiles.wordpress.org/drewapicture/) (1), [@dd32](https://profiles.wordpress.org/dd32/)(
1), [@Mike_Cowobo](https://profiles.wordpress.org/mike_cowobo/) (1), [@TimothyBlynJacobs](https://profiles.wordpress.org/timothyblynjacobs/)(
1), [@rmccue](https://profiles.wordpress.org/rmccue/) (1), [@lukecarbis](https://profiles.wordpress.org/lukecarbis/)(
1), [@donmhico](https://profiles.wordpress.org/donmhico/) (1), [@chriscct7](https://profiles.wordpress.org/chriscct7/)(
1), and [@shital-patel](https://profiles.wordpress.org/shital-patel/) (1).

**Congrats to our 2 new contributors of the week:** [@silb3r](https://profiles.wordpress.org/silb3r/),
and [@Mike_Cowobo](https://profiles.wordpress.org/mike_cowobo/) ♥️

**Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
7), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (4), [@desrosj](https://profiles.wordpress.org/desrosj/)(
4), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) (2), [@gziolo](https://profiles.wordpress.org/gziolo/)(
2), and [@jorbin](https://profiles.wordpress.org/jorbin/) (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/)
2:51 pm _on_ April 26, 2021     
Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/),
[core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/),
[meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)   

# 󠀁[Editor Chat Agenda: 28 April 2021](https://make.wordpress.org/core/2021/04/26/editor-chat-agenda-28-april-2021/)󠁿

Facilitator and notetaker: @jorgefilipecosta

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, April ](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210428T16&p1=187&ah=1)
[2](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210428T16&p1=187&ah=1)
[8](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210428T16&p1=187&ah=1)
[, 2021, 0](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210428T16&p1=187&ah=1)
[4:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210331T10&p1=2157&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/)._

 * GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
   The editor improves the process and experience of creating new content, making
   writing rich content much simpler. It uses ‘blocks’ to add richness rather than
   shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   10.5 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/40/?output_format=md#alpha-beta).
   release.
 * [Full Site Editing Go/No Go: Next steps](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/).
 * [IE 11 support phase out plan.](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/)
 * [Monthly Plan for April 2021](https://make.wordpress.org/core/2021/04/08/whats-next-in-gutenberg-april-2021/)
   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.
    - Full Site Editing.
 * 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/), 
[#meeting](https://make.wordpress.org/core/tag/meeting/)

 [  ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/)
1:55 pm _on_ April 26, 2021     
Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/),
[core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/),
[editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/),
[meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/)   

# 󠀁[Editor chat summary: Wednesday, 21 April 2021](https://make.wordpress.org/core/2021/04/26/editor-chat-summary-wednesday-21-april-2021/)󠁿

This post summarizes the latest weekly Editor meeting ([agenda](https://make.wordpress.org/core/2021/02/15/editor-chat-agenda-17-february-2021/),
[slack transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1619013664056300)),
held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
channel, on[ Wednesday, April 21, 2021, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210421T1400).

Thank you to all of the contributors who tested the BetaBeta A pre-release of software
that is given out to a large group of users to trial under real conditions. Beta
versions have gone through alpha testing in-house and are generally fairly close
in look, feel and function to the final product; however, design changes often occur
as part of the process. releases and gave feedback. Testing for bugs is a critical
part of polishing every release and a great way to contribute to WordPress.

## Full Site Go/No Go

The [Full Site Editing Go/No Go](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/)
demo took place a few days ago, where project leadership determined what new features
should be included in WordPress 5.8 based on their current status, feedback gathered
in calls for testing, and the prospect of achieving a solid implementation before
the feature freeze.

As a next step [high-level overview](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)
of the focuses to attend to before the feature freeze is defined. [WordPress 5.8 FSE must-haves](https://github.com/WordPress/gutenberg/projects/55#card-59207760)
project board is available to trace individual items.

## GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. 󠀁[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)󠁿 10.4

Gutenberg 10.4 was released on [14th April ](https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/)
introducing cool features like 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. widgets in the CustomizerCustomizer Tool built into WordPress
core that hooks into most modern themes. You can use it to preview and modify many
of your site’s appearance settings., enhancements to the Site Editor, improvements
to rich text placeholders, and, as always, many bugbug A bug is an error or unexpected
result. Performance improvements, code optimization, and are considered enhancements,
not defects. After feature freeze, only bugs are dealt with, with regressions (adverse
changes from the previous version) being the highest priority. fixes as well.

## Gutenberg 10.5 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/40/?output_format=md#alpha-beta)󠁿.

[Gutenberg 10.5 RC 1 ](https://github.com/WordPress/gutenberg/releases/tag/v10.5.0-rc.1)
was released last week test and report bugs.

## FSE Outreach

Two weeks remaining to go on a Query (block) Quest with the fse [outreach expirement](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/).

## Monthly Plan

The monthly update containing the high-level items that Gutenberg contributors are
focusing on for January are:

 * Global Styles.
 * Block-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.
 * Full Site Editing.

For detailed plan check out [monthly priorities](https://make.wordpress.org/core/2021/02/01/whats-next-in-gutenberg-february-2021/)
post.

## Updates on the key projects

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

A brief update on Widgets and Navigation:

 * Focus on figuring out the best approach for backward compatibility and see how
   much can the block based editor offer.
 * Navigation editor progressed with bug fixes, but still hanging around the coreCore
   Core is the set of software required to run WordPress. The Core Development Team
   builds WordPress. issues of how to best reuse the navigation block.

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

This week in global styles:

 * Landed 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. with elements [#29891](https://github.com/WordPress/gutenberg/issues/29891).
 * extract sanitization method [#30809](https://github.com/WordPress/gutenberg/pull/30809).
 * Added block support & theme.json support for: border-color, border-style, and
   border-width [#30124](https://github.com/WordPress/gutenberg/pull/30124).
 * Clean cached data when switching themes [#30830](https://github.com/WordPress/gutenberg/pull/30830).
 * Standarize block editor settings load [#30245](https://github.com/WordPress/gutenberg/pull/30245).
 * Fix regressionregression A software bug that breaks or degrades something that
   previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2021/page/40/?output_format=md#blocker).
   Recent regressions may be given higher priorities. A "3.6 regression" would be
   a bug in 3.6 that worked as intended in 3.5. in color panel of global styles 
   sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used
   by WordPress themes to display information that is not a part of the main content.
   It is not always a vertical column on the side. It can be a horizontal rectangle
   below or above the content area, footer, header, or any where in the theme. [#31015](https://github.com/WordPress/gutenberg/pull/31015).
 * Add utility to retrieve classes and styles in color hook [#30869](https://github.com/WordPress/gutenberg/pull/30869)
   [#30870](https://github.com/WordPress/gutenberg/pull/30870).
 * Polish color labels [#30075](https://github.com/WordPress/gutenberg/pull/30075).
 * changes to shape (working in all editors & front-end) [#30541](https://github.com/WordPress/gutenberg/pull/30541).
 * Allow skipping serialization for typography attributes [#30880](https://github.com/WordPress/gutenberg/pull/30880).
 * Conversation about “overlay” colors [#29963 (comment)](https://github.com/WordPress/gutenberg/issues/29963#issuecomment-820494790).
 * Migrate more blocks using the skipSerialization mechanism as well as adding more
   properties [#2891](https://github.com/WordPress/gutenberg/issues/28913).
 * kses filtering (approved) [#30888](https://github.com/WordPress/gutenberg/pull/30888).

The priority continues to be shipping [#29891](https://github.com/WordPress/gutenberg/issues/29891)
as soon as possible to unblock related work.[#28913](https://github.com/WordPress/gutenberg/issues/28913)
is a good issue to look at if you can lend a hand (help with reviews, migrate more
blocks, more properties, etc).

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

Navigation block improvements follow all [the details in the tracking issue here](https://github.com/WordPress/gutenberg/issues/27593).

 * Responsive menu is close and got delayed due to external priorities, but I’d 
   expect in 10.6.
 * Home Link has started new since last time.

## Task Coordination

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

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

 * Created partial fix for [image duplication issue](https://github.com/WordPress/gutenberg/pull/30891)
   when changing alignment during upload.
 * Added [media width control](https://github.com/WordPress/gutenberg/pull/31002)
   to Media & Text block.Started working on some Navigation Editor issues:
 * Fix [navigation saving issue](https://github.com/WordPress/gutenberg/pull/31028)
   with WP subdirectory setups.
 * Moved the “Delete menu” button to the [bottom of the sidebar](https://github.com/WordPress/gutenberg/pull/31026).

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

Focusing on the navigation block, looking into patterns.

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

 * Working on a few issues for Learn.
 * VVV/Vagrant setup a local dev environment tutorial.
 * Exploring improvements to the Page templates UIUI User interface.

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

_Quick update from the native mobile folks:_ 

 * Block transforms, Interim dual-license for new contributions merged, media insertion
   flow simplification.
 * Gallery Block Refactor Resumed, Editor Onboarding implementation started.
 * Fixes in Stepper a11yAccessibility Accessibility (commonly shortened to a11y)
   refers to the design of products, devices, services, or environments for people
   with disabilities. The concept of accessible design ensures both “direct access”(
   i.e. unassisted) and “indirect access” meaning compatibility with a person’s 
   assistive technology (for example, computer screen readers). (https://en.wikipedia.
   org/wiki/Accessibility), Unsupported Block Editor start, Quote block citation
   newlines.
 * Refined media progress error notice.
 * _In Progress_: GSS, Reusable blocks, Search block, Block Picker Search, Embed
   block, Slash inserter.

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

Published a PR with a proposal introducing a [document defining some Gutenberg Principles](https://github.com/WordPress/gutenberg/pull/30963/files)
for the project to adopt. Would be good to get more eyes on it (especially from 
the coreteam).

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

 * Merged [suggesting block patterns in block placeholder](https://github.com/WordPress/gutenberg/pull/29602)
   states.
 * Site Title enhancements(toolbar normalization, add default block after pressing
   enter at the end of the title).

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

 * [Organizing block API reference](https://github.com/WordPress/gutenberg/pull/30980)
   in handbook.

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

 * Work on the Navigation editor/screen.
 * Focused on ensuring wp nav menu items are mapped to the correct block types/variations
   [#31004](https://github.com/WordPress/gutenberg/pull/31004).
 * Exploring a [clearer “close” UX](https://github.com/WordPress/gutenberg/pull/30964)
   for the Site Editor navigation sidebar that appears when you click the `W` icon.

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

 * Focused on the FSE Outreach Program (responding to feedback, amplifying, testing,
   writing up the latest summary).
 * Alongside a work in progress core editor improvement post and a post on the role
   of the Gutenberg pluginPlugin A plugin is a piece of software containing a group
   of functions that can be added to a WordPress website. They can extend functionality
   or add new features to your WordPress websites. WordPress plugins are written
   in the PHP programming language and integrate seamlessly with WordPress. These
   can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party./when to .use Gutenberg for `/
   news` to help guide people.

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

 * Merged a simple implementation for [skip-links in block templates](https://github.com/WordPress/gutenberg/pull/30336).
 * Working on [auto-generating anchors for headings](https://github.com/WordPress/gutenberg/pull/30825).
 * Working on fixing non-px values in controls (there’s currently an issue and everything
   is px-only) lots of PR reviews
 * Will be focusing on tickets required for WP5.8.

## Open Floor

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

 * Block Transforms: deprecating `transform` 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. in favour of `convert`
   for block transforms.
 * When the group block was introduced we had to create a new experimental API `
   convert` to allow us to group a block/selection of blocks via the “Block Transform”
   UI in the block toolbar.
 * This was because [the existing `transform` API](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-transforms/)
   only provided access to a limited set of data about the block(s) being transformed,
   whereas we needed the blocks _themselves_.
 * In many cases it is more useful to simply receive the block(s) being transformed–
   this provides access to all data about the block (including `attributes` and `
   innerBlocks`). This is (for the most part) a “blocks in, blocks out” mindset 
   which feels quite natural.
 * **@**aduth [proposed we promote the `convert()` API and deprecate `transform`](https://github.com/WordPress/gutenberg/pull/19401).`
   transform` would remain in place for backwards compatibility so there would be
   no breakage. The API has been in use for over a year but is not standardised 
   or documented. Also, it cannot easily be removed as the Group block is dependent
   on it.
 * The PR has fallen dormant and needs a decision to take it forward. I’m happy 
   to help do the work to get it over the line if we can wrangle a decision.

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

 * I am working on the flow of the Page template and I am seeing a few things here
   and there that needs adjusting. One issue I have met a few times is the lack 
   of [ability to discard a save](https://github.com/WordPress/gutenberg/issues/31043).
   I made this issue showing how one gets stuck. 
 * There are explorations going on in relation to discarding saves but it is more
   complex.

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

 * I would love to get UXUX User experience feedback on this [issue](https://github.com/WordPress/gutenberg/pull/30891)
   and if it’s okay to hide block controls while an image is uploading.

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

 * Right now I can’t use any non-px values. We can’t say that font-size should be`
   2em` and I suspect that’s from g2. Things that were supposed to work don’t (paddings).
   If anyone is able to use non-px values for paddings in latest trunktrunk A directory
   in Subversion containing the latest development code in preparation for the next
   major release cycle. If you are running "trunk", then you are on the latest revision.,
   please let me know how… Right now I can’t see how it could possibly work, it 
   looks like `units` is **always** an empty array and I can’t figure out how/why
   it was working in the old days

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

 * I was just curious to know if anyone had any requests for hallway hangout ideas.
   As a reminder, hallway hangouts are meant to be gatherings for more casual collaboration
   and learning whether through zoom, twitch, etc. For example: [https://make.wordpress.org/test/2021/04/08/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-8-april/](https://make.wordpress.org/test/2021/04/08/hallway-hangout-discussion-on-full-site-editing-issues-prs-designs-8-april/)
   [8:23](https://wordpress.slack.com/archives/C02QB2JS7/p1619016787121800)It’s 
   been a while since I explicitly asked and I like to do some wrangling when I 
   can to get topics people want to see covered

[Read complete transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1619013664056300)

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

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
8:41 pm _on_ April 23, 2021     
Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/),
[core-editor-improvement ( 35 )](https://make.wordpress.org/core/tag/core-editor-improvement/),
[gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/)   

# 󠀁[Core Editor Improvement: Refining the Block Toolbar](https://make.wordpress.org/core/2021/04/23/core-editor-improvement-refining-the-block-toolbar/)󠁿

With a growing amount of customization features being unlocked, the toolbar for 
each coreCore Core is the set of software required to run WordPress. The Core Development
Team builds WordPress. 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. is being transformed one at a time to make it more intuitive and
predictable to use. Since the block toolbar contains the most important block tools,
this could help improve your workflow as you’re creating content.

In the same way you might organize tools in a toolbox so you can quickly grab and
go, the toolbar is on that same path: grouping related tools based on which level
of a block an option impacts. To get a sense of what this actually means, and how
it’ll improve your workflows here’s a before and after photo showing the changes
in the Image Block:

**Before:**

[⌊Image showing the block toolbar on an Image Block with the tooling before the 
update occurred. ⌉⌊Image showing the block toolbar on an Image Block with the tooling
before the update occurred. ⌉[

**After:**

[⌊Image showing the block toolbar on an Image Block with the tooling after the update
occurred. ⌉⌊Image showing the block toolbar on an Image Block with the tooling after
the update occurred. ⌉[

Keep in mind that not all blocks have been revamped just yet, but you can [follow this issue to keep track](https://github.com/WordPress/gutenberg/issues/25983).
For now, if you’re using the 10.4.1 release of the GutenbergGutenberg The Gutenberg
project is the new Editor Interface for WordPress. The editor improves the process
and experience of creating new content, making writing rich content much simpler.
It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
pluginPlugin A plugin is a piece of software containing a group of functions that
can be added to a WordPress website. They can extend functionality or add new features
to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party., you can expect to see this update
in the following blocks, with more on the way: 

 * Image 
 * Cover
 * Button
 * Buttons
 * List
 * Heading
 * Paragraph
 * Quote
 * Audio
 * File
 * List
 * Video
 * Media & Text
 * Site Logo
 * Post Featured ImageFeatured image A featured image is the main image used on 
   your blog archive page and is pulled when the post or page is shared on social
   media. The image can be used to display in widget areas on your site or in a 
   summary list of posts.

The goal of the effort is to simplify the hierarchy of the block, to make it more
predictable what goes where. Here’s a visual outlining the groupings:

![](https://lh5.googleusercontent.com/kf72_cibTgky9DybMkusr1PVi_yZusqpnUudLkpI7JRlYahQOABNZ1kaq6vHH8keD9ZICldoQKxedANkyAkYzTkFQaa8uzp1kmxHCb9irbWtsK63hQNuUtJxOKTVVEby2c8d0vPr)

The visual is taken from [recently updated documentation](https://developer.wordpress.org/block-editor/how-to-guides/designers/block-design/#group-block-toolbar-controls-with-related-items):

 * **Block **surfaces properties of the block itsef..
 * **Tools** surfaces tools that affect the whole content of the block, such as 
   alignments or positition.
 * **Inline formatting **refers mostly to in-text transformations such as bold or
   italic on a text selection. 
 * **Other** contains any additional features that do not fit in the other groups.

As each core block gets updated, there will hopefully be a cascading effect, making
it predictable to adjust any block how you need to, whether that’s changing block
alignment or bolding a specific piece of text.  

_Thank you to [@joen](https://profiles.wordpress.org/joen/) for helping edit this
post (including providing the visuals) and for the excellent guidance throughout._

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

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
6:29 pm _on_ April 23, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[planning ( 36 )](https://make.wordpress.org/core/tag/planning/)   

# 󠀁[WP5.8 Squad Call for Volunteers](https://make.wordpress.org/core/2021/04/23/wp5-8-squad-call-for-volunteers/)󠁿

_Edit: 4/23/2021 @ 19:10 UTC – changed the references to contributors in the last
paragraph to WordPress.orgWordPress.org The community site where WordPress code 
is created and shared by the users. This is where you can download the source code
for WordPress core, plugins and themes as well as the central location for community
conversations and organization. [https://wordpress.org/](https://wordpress.org/)
usernames to help to make the connection. – [@desrosj](https://profiles.wordpress.org/desrosj/)_

With the schedule finalized and parts of 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/)
phase 2 getting ready to merge, it’s time to put together a squad of focus leads
for WordPress 5.8.

You can read more about the [different roles in the handbook](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/).

Here are the squad roles available:

 * [Release Coordinator](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#release-co-ordinator)
 * [Triage Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#triage-lead)
 * [Core Tech Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#core-tech-lead)
 * [Core Design Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#core-design-lead)
 * [Documentation Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#documentation-wrangling)
 * [Editor Tech Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#editor-tech-lead)
 * [Editor Design Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#editor-design-lead)
 * [Accessibility Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#accessibility-lead)
 * [Support Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#support)
 * [Test Lead](https://make.wordpress.org/core/handbook/about/release-cycle/wordpress-release-team-and-focus-leads/#test)

The roles of release leadRelease Lead The community member ultimately responsible
for the Release. and marketing/communications lead will be filled by [@matt](https://profiles.wordpress.org/matt/)
and [@chanthaboune](https://profiles.wordpress.org/chanthaboune/), respectively.

## Expectations

Focus leads should be available for at least 5-6 hours a week to perform their tasks,
with more time as milestones like Betas, Release Candidates, and General release
approach. On the days of those milestones, you might need to dedicate 4-6 hours 
to WordPress on one day.

There are no limitations to where you come from. We are a global community, open
24/7 so you will schedule scrubs, if needed, according to your availability and 
potentially find a deputy to cover other timezones.

Because 5.8 is going to be a busy release, the squad won’t have mentorship or ride-
along opportunities, like it did in the past, but as [Josepha mentioned](https://make.wordpress.org/core/2021/03/12/early-thoughts-on-wp5-8-planning/)
there is a [public channel for the team to coordinate](https://wordpress.slack.com/archives/C01VACX5E2W)
so that others can learn through observation.

This doesn’t mean you need to have all the answers to volunteer. 🙂 There will be
a bunch of people available to help and support (the CoreCore Core is the set of
software required to run WordPress. The Core Development Team builds WordPress. 
team representatives, long-time contributors, etc…).

## Are you interested?

Please leave your name in the comments with the role you are interested in or reach
out to me ([@francina](https://profiles.wordpress.org/francina/)), [@audrasjb](https://profiles.wordpress.org/audrasjb/)
or [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) if you have any
questions before raising your hand.

Thanks!

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

 [  ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/)
10:38 pm _on_ April 22, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/)

# 󠀁[IE 11 Support Phase Out Plan](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/)󠁿

After [recent research and discussion](https://make.wordpress.org/core/2021/03/04/discussion-dropping-support-for-ie11/),
a decision to drop Internet Explorer 11 support in WordPress [was reached](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/).
However, the timing for this change was undetermined when the summary post was published.

After discussing with several contributors, the decision has been made to move ahead
with **officially removing IE11 support in WordPress 5.8.**

**Note:** This change will only affect WordPress and it’s built-in features. For
your site visitors, any 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. or theme you may be using, which
was made with support for IE11 in mind, should still look and feel as if nothing
changed.

## Phase-Out Plan

IE11 support will be removed in two phases.

### Phase 1: WordPress 5.8

For 5.8, the following steps will be taken:

 * Update the `browserslist` for the `package.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.`
   file in `trunktrunk A directory in Subversion containing the latest development
   code in preparation for the next major release cycle. If you are running "trunk",
   then you are on the latest revision.`.
 * Run the build process to update generated CSSCSS Cascading Style Sheets..
 * Update the `browserslist` in the GutenbergGutenberg The Gutenberg project is 
   the new Editor Interface for WordPress. The editor improves the process and experience
   of creating new content, making writing rich content much simpler. It uses ‘blocks’
   to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   repository to remove IE11 support from built CSS and JSJS JavaScript, a web scripting
   language typically executed in the browser. Often used for advanced user interfaces
   and behaviors..

This will effectively remove IE11 support in the blockBlock Block is the abstract
term used to describe units of markup that, composed together, form the content 
or layout of a webpage using the WordPress editor. The idea combines concepts of
what in the past may have achieved with shortcodes, custom HTML, and embed discovery
into a single consistent API and user experience. editor and all generated CSS files
used within the adminadmin (and super admin).

A TracTrac An open source project by Edgewall Software that serves as a bug tracker
and project management tool for WordPress. ticketticket Created for both bug reports
and feature development on the bug tracker. will be opened to discuss whether IE11
specific polyfills should continue to be enqueued in WordPress 5.8. Even if polyfills
are not loaded, they will remain bundled with CoreCore Core is the set of software
required to run WordPress. The Core Development Team builds WordPress. in case plugins
or themes wish to continue loading them.

**New features added in 5.8 or later do not need to be tested on or support IE11.**

### Phase 2: WordPress 5.9 and beyond

Because most of the code in WordPress Core targeting specific browsers maintained
manually (not compiled or run through a build process), individual tickets should
be created to evaluate removing each instance of IE11 specific code.

These tickets **will not be considered in 5.8** unless a committercommitter A developer
with commit access. WordPress has five lead developers and four permanent core developers
with commit access. Additionally, the project usually has a few guest or component
committers - a developer receiving commit access, generally for a single release
cycle (sometimes renewed) and/or for a specific component. or release squad member
feels it is a blockerblocker A bug which is so severe that it blocks a release. 
for full site editing and agrees to own the ticket.

_Props [@jorbin](https://profiles.wordpress.org/jorbin/), [@chanthaboune](https://profiles.wordpress.org/chanthaboune/),
[@Clorith](https://profiles.wordpress.org/clorith/), [@youknowriad](https://profiles.wordpress.org/youknowriad/),
and [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) for discussing
the above plan and reviewing before being published._

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

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
10:35 pm _on_ April 22, 2021     
Tags: [make.wordpress.org/test ( 29 )](https://make.wordpress.org/core/tag/make-wordpress-orgtest/),
[p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)   

# 󠀁[X-post: Upcoming FSE Outreach Program Schedule](https://make.wordpress.org/core/2021/04/22/xpost-upcoming-fse-outreach-program-schedule/)󠁿

X-comment from [+make.wordpress.org/test](https://make.wordpress.org/test/): Comment
on [Upcoming FSE Outreach Program Schedule](https://make.wordpress.org/test/2021/04/22/upcoming-fse-outreach-program-schedule/#comment-1503)

# Post navigation

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

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