CSS Chat Summary: 2nd April 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1585861240051700

I (@isabel_brison) facilitated the meeting. 

CSS audit updates

  • @notlaura tested Parker, a stylesheet analysis tool, with results documented here.
  • @joyously suggested CSS Stats as another potential tool.
  • The a11y team had a look at the audit tickets at their weekly meeting and had a few recommendations.
  • Based on a11y team feedback, we agreed to add notes to the audit on any CSS properties we find that are unhelpful for accessibility.

Open Floor

@joyously requested we add a channel topic to #core-css, with the time of our weekly meeting, which we did.

@joyously asked if the audit would include editor CSS, or only wp-admin pages. The current audit includes only wp-admin pages, but there was agreement on auditing both the editor and the default themes CSS at a later stage.

That was all for this week!

Next week @notlaura will be taking over the running of this meeting, due to daylight savings changes.


Dev Chat summary – April 1, 2020

@davidbaumwald led the chat on this agenda.

Full meeting translate on Slack.

This is the first devchat after the release of WordPress 5.4.


WordPress 5.4 “Adderley” was released yesterday, March 31, 2020 as scheduled.

@audrasjb shared the stats for contributors to the release. There was a total of 552 contributors from 48 countries, 32% of them being new contributors. For more accurate release contributors statistics, please fill in your WordPress profile (if you want).

Highlighted Blog Posts

@davidbaumwald shared the posts of Core Privacy team about the WP Consent API feature plugin proposal and the Guidelines for Internet Explorer 11 support in WordPress.

Upcoming Releases

@davidbaumwald reminded that 5.5 has been in Alpha phase for a while now.

Components Check-in

@audrasjb announced the release of version 0.4 of Auto-updates plugin which contains all features initially planned fot the project; as well as Themes updates and email notifications. Design, copy and accessibility reviews and feedback are welcome from plugin authors and WordPress developers.

Open Floor

@howdy_mcgee called for a feedback on these old Trac tickets: #29418, #39447, #46768, #37245, #38074, #37255 and #24142.

@azaozz shared the link of WordPress 5.4 master list in support forums. Please, go through this before posting a topic in the forums.

@ipstenu and @azaozz called for attention on respectively these two tickets #49753 and #4975, related to 5.4.

@howdy_mcgee pointed to #24780 and said he has made a document to track the supression operators in Core codebase.

@jeffpaul asked we should start taking a look at the 5.5 early tickets to review patches and look to get some of those in sooner. Here’s for reference the Trac query for 5.5 tickets.

@jeffpaul also suggested to schedule an early-specific bug scrub in the next couple of weeks to help move those tickets along. A few people voluntereed to lead these scrubs.

@bph reminded that the WPBlockTalk is happening on April 2, and everyone is welcome to register here.

#5-4, #5-5, #dev-chat, #summary

CSS Chat Agenda: 2nd April 2020

This is the agenda for the upcoming CSS meeting scheduled for 2nd April, 21:00 UTC.

This meeting will be held in the #core-css channel  in the Making WordPress Slack.

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


  • CSS audit status update
  • Open floor

#agenda, #core-css

Editor chat summary: 2020 April 1

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, April 1, 2020, 14:00 UTC. These meetings coordinate collaboration in the development evolution of the Gutenberg project. Today’s agenda found here: 


Gutenberg 7.8.0 released last week

WordPress 5.4 Release 31 March 2020 – Field Guide
No incidents happened during the release and it already contains 2.6 million downloads

Weekly Priorities

  • The team reached a milestone closing 10,000 PRs
  • The April plan is published and includes
    • Full Site Editing: Continue improving the Edit Site screen and blocks
    • Global Styles: This will be a big one this month (support in blocks and UI)
    • Updated Inserter UI to support patterns and blocks
    • Updated Navigation/Menus screen
    • Continue G2 iterations
  • Release of 7.9 will be pushed one week to account for additional work on Global Styles project that can have some impact on themes. The extra week would be useful to polish the global styles support across different blocks and document the potential impacts properly. 
  • Release of 5.4.1 is not scheduled. Please mark PR’s/issues with `Backport to WP Core` and keep an eye for potential high impact issues that we may want to include in it.

Task Coordination


Besides the release, last Friday, we also did a WordPress 5.4 RC 5 that included some fixes to problems discovered with the editor. More details of the fixes can be found here and here.

The Good news is WordPress 5.4 is out with no incidents reported during the release and It already has 2.6 million downloads. The situation in the world was far from normal, but we managed to take the release to the finish line and solve the critical issues as soon as they were discovered/reported, so thank you a lot to all that made this possible


  • Block support for some of the Global styles variables (mainly colors)
  • Patterns API and UI


  • Pushing forward Global Styles at edit-site
  • Making font-size an implicit attribute of the block.
  • For next week, carry on with those and revive this exploration for Global Styles that uses general variables while allowing for targeting specific blocks.


  • Supporting release a bit with forums
  • Feedback flow: global styles
  • Navigation: focusing back on block and nav-menus.php
  • Triage always be triaging


  • Helping stabilize build failures to help unblock people from their work.
  • Prompting new contributors to link their GitHub account for props PR 21221 is now merged
  • A few other developer experience related improvements


  • Starting last week I am focusing back on Navigation block and nav-menus.php
  • Work from the past two weeks is blocked by lack of reviewers. There are several PRs open and waiting for reviews / comments with new features for the Latest Posts block. 


  • Continue to work on “Design Tool” issues 
  • Continue adding/improving style attributes to blocks to enable better customization

PRs Needing Review

Refactor ReusableBlockEditPanel to use hooks (and add type info) 21181
Navigation block: show color controls in toolbar only. 20884 
[Latest Posts] adds author option to latest posts block 20595
Refactor ReusableBlockEditPanel to use hooks (and add type info)  21181
Add tags in latest posts block 20785
Table of Contents block 21234
Insert post title instead of URL, when adding a link to an existing post 21240 
This issue needs review for a possible PR:
Bug: Link sometimes embeds other times not. 21029 

Open Floor

@julescole PR 21240 Insert post title instead of URL, when adding a link to an existing post

@tobifjellner WordPress TracAPP  #49752 Layout issue in WP 5.4 Needs design feedback

@paaljoachim I am very hyped on @shaunandrews PR 21121 as I believe it would make going in and out of full screen a lot easier. But we can wait and see what kind of feedback shows up in regards to the full screen mode that is included in 5.4. (edited) 

@paaljoachim I think the Embeds bug issue would fit nicely into 5.4.1. There are multiple aspects to it.

@zebulan For fun, I made a PR to refactor ReusableBlockEditPanel to use hooks. I have no idea if it runs faster (or how to even test that), but the code feels cleaner to me. Also, the PR adds JSDoc type information. Reviews/feedback are welcome as always. Also can use some eyes on a Table of Contents PR.


Having an issue with not being able to grab unpublished permalinks. You can read more about it in core-js but the gist of it is that I’m not sure where the change should occur.


When we actually click to preview it, it can’t use the future permalink because it isn’t live yet. That won’t route and will return a 404. So we have to use the ?p=123 type link for the href on scheduled posts. But we could generate what it would look like using the permalink template and placeholders

What’s next in Gutenberg? (April)

This is a monthly update containing the high-level items that Gutenberg contributors are focusing on for the next month. Join us in our efforts.

Full Site Editing

Work on this major focus is ongoing and is expected to continue iterating over the next months.

The team is still working on the Edit Site UI in order to bring parity with the Post Editor, support more template-management related features and improve the FSE blocks.

The important tasks have been splitted into sections and highlighted on this overview issue.

Global Styles

The Global Styles work is a major focus for this month. One of the most important aspect here is to add support for the global styles configurations (variables) to multiple blocks.

Some blocks have already been updated to support color settings and line height. This trend is expected to continue and expand to other settings and other blocks.

At the same time, the Global Styles UI is being iterated on the Edit Site screen.

You can follow the progress of this project on this overview issue.

Patterns & Inserter UI

Recently, the Patterns feature and APIs have been added to the editor. The UI is still experimental and an overall redesign of the inserter to absorb both blocks and patterns is one of the month’s priorities.

The team will continue to explore adding more patterns. This highlighted a need for more advanced block tools and customizations.

Updated Navigation Screen

A new experimental Navigation Menu screen is being explored and will serve as a block-based replacement for the existing menus page.

Refining the interface

The previous releases saw a big UI update for the editor. The team will continue to iterate based on the remaining tasks and the user feedback.

While these are our focuses don’t forget you can always help with triage, needs testing issues, good first issues and reviewing PRs.


CSS Chat Summary: 26th March 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1585256425000800

I (@isabel_brison) facilitated the meeting. 

CSS audit updates

  • I looked into our possibilities for visual regression testing and found that jest-image-snapshot integrates very well with our existing e2e testing tools. I’m preparing a prototype branch that I will share on the ticket soon.

Open Floor

@sabernhardt requested feedback on a patch for adding print styles to wp-admin. Discussion ensued, and we agreed that:

  • Currently, when printing out wp-admin, the only thing that doesn’t show is the admin bar. This is not optimal, and print styles should remove all interface features not relevant to page content.
  • The print styles should apply to all wp-admin pages that have content and/or lists.
  • Work on the initial ticket should attempt to hide all common interface elements for print
  • If much further work is needed on individual pages, we should create sub-tickets for easier tracking/review.

And that was all for this week!

#core-css, #summary

Dev Chat summary – March 25, 2020

@francina facilitated the chat on this agenda.

Full meeting transcript on Slack

This devchat marked week 11 of the 5.4 release cycle.


WordPress 5.4 Release Candidate 4 was released on Tuesday March 24, 2020 and everything went smoothly.

@audrasjb shared an update on WP Auto-updates Feature Plugin: it was moved from his personal GitHub account to WordPress/wp-autoupdates which is the new official GitHub repository of this project. The #core-auto-updates team will try to ship version 0.4 before WP 5.4 is released. This new version aims to handle auto-updates for themes.

@afragen asked for a review of some Trac tickets which are all associated with Theme compatibility checks and will likely have interaction with the auto-updates feature. The idea is to ship them early in WordPress 5.5.

@whyisjake pointed out that he really like the work that is going on in #core-auto-updates Slack channel and think that trying to land in the next few releases would be excellent. Related, He’d love to see #core-passwords (two-factors authentification – 2FA) land in core too. In his opinion, the plugin is so mature at this point that having it left out almost seems like an omission. @whyisjake is going to work on a merge proposal.

@clorith raised that it would be necessary to make sure that the 2FA proposal also highlights the concerns with how to address users locking them selves out (which was the major holdback previously).

@azaozz announced that the patch for image lazy-loading attribute is ready for testing.

Upcoming Releases

The current major is 5.4, scheduled to go out on March 31st 2020; please keep testing for all the bugs!

There are two ways do it:

Trunk has been branched to 5.5 on the beginning of March. That means 5.5 is officially in Alpha.

@francina announced that work for 5.6 –which is going to be an all-women release– has kicked off with an initial round of messages going out to the women that expressed interest. @angelasjin @francina and Chloé Bringmann are contacting them to hear if they are still interested, what skills they have and what expectations.

Components Check-in

@francina shared a proposal to change the Components Check-in. This is always done towards the end of the chat and feels rushed. There is never really time to dig into the topics they might bring up. Francesca shared two ideas:

  1. Schedule a weekly post where they can leave their status update, like the one for Community deputies.
  2. Adopt a Slack Bot that once a week will ask the maintainers for a status update: maybe in a new component-maintainers Slack channel. Core is getting very busy with Trac and Travis bots, and RSS.

@johnbillion added that trying a weekly post could be a good idea. Maybe every Tuesday so it’s ready for the dev chat on Wednesdays in case anything comes up.

@francina proposed to talk to #meta to set this up and test drive it for 8 weeks.

Open floor

@isabel_brison proposed to create a set of guidelines for Internet Explorer support. The CSS team kind of decided on starting to deprecate it, and “graceful degradation” seems a good way to go forward, meaning Core can use unsupported technology to make non-essential enhancements. Isabel wants to agree on what’s “essential” here, and created a Trac ticket to start the discussion: #49696

@paaljoachim suggested to punt default full screen mode to 5.5 as there is a pull request on Gutenberg project GitHub repository to provide an alternative approach.

@audrasjb pointed out that the proposal in this pull request would be a way better than the current implementation.

@whyisjake added that this is not a realistic change for WP 5.4, it’s a proof of concept, and not a fully tested feature.

@francina confirmed that @matt took the decision to ship WordPress 5.4 with this feature. Matt also commented in the Accessibility Team statement post.

@joyously stated it’s hard to contribute when concerns are ignored. @chanthaboune answered she can understand how they can feel ignored. A lot of that research gets done solo, and it’s often hard to remember to recap your own research. For full site editing to be a reality by the end of the year, the work can start bringing incremental changes. This change is feeling very jarring, but there is more worry about not have any mid-point between here and Full Site Editing.

@peterwilsoncc, @clorith and @audrasjb agreed that since RC4 was released, it’s not realistic to revert this change. The discussion can continue in a post-mortem post on Make/Core.

#5-4, #5-5, #5-6, #dev-chat, #feature-autoupdates, #feature-lazyloading, #two-factor

CSS Chat Agenda: 26th March 2020

This is the agenda for the upcoming CSS meeting scheduled for 26th March, 21:00 UTC.

This meeting will be held in the #core-css channel  in the Making WordPress Slack.

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


  • CSS audit status update
  • Open floor

#agenda, #core-css

JavaScript Chat Summary – March 24, 2020

Below is a summary of the discussion from this week’s JavaScript chat (agenda, Slack Transcript)

Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Agenda: Date module dateI18n gmt parameter (added by @davilera)

Slack | Pull Request

This is a pull request that has been around for a while and David has addressed all the feedback given so it’s ready for merge.

Action: @iandunn pinged to verify the latest round of changes and that it tests good.

Agenda: Module naming and deprecations (added by @aduth)

Slack | Github and Comment including links to previous discussions

Topic concerns aligning naming conventions for wp globals on package exports.


  • Merge pull #18722 that documents how to use ServerSideRender from the wp.serverSideRender export. (Done)
  • Create an issue to track the broader effort of “fixing” the names for these globals. (Done)

News Roundup

This roundup contains a few links for Gutenberg and JavaScript related news curated (and commented on) by @nerrad

Other Random Stuff

#javascript, #meeting-notes

XML Sitemaps Meeting: March 24th, 2020

In case you were looking for an blog post about the XML Sitemaps feature project last week, worry no more. Work on the plugin is progressing smoothly and steadily, we just didn’t publish an agenda post last week. That means it is time for a double update today!

Meeting Recap: March 10th & 17th

For reference, check my previous blog post from March 10th:

A lot has happened since then. Here’s the summary, not necessarily in the right order:

  • SimpleXML dependency
    We received great feedback from a variety of big hosting providers, all saying that this PHP extension is widely available and we can rely on it safely.
    Current status: no action needed.
  • Rewrite rule conflict with plugins
    As we realized that the new /wp-sitemap.xml URL format clashes with big existing plugins, we decided to look into alternate names for both the rewrite rules as well as the query params. See GitHub issue for details.
    Current status: needs contributors.
  • Rewrite rule issues with custom providers
    It was reported that adding custom sitemap providers might require flushing rewrite rules. Ideally, that shouldn’t be needed.
    Current status: needs decision.
  • Last modified date (lastmod)
    We decided to continue with the proposed PR to remove lastmod from sitemaps (at least for now), but need to make sure there is appropriate documentation. It’s something that can always be added back if needed.
    Current status: has PR, needs documentation.
  • Query Filters
    Valuable feedback emerged from testing, which led to the decision to close the existing PR to make query instances filterable in favor of a simpler approach. In its place, we should make the query arguments filterable, and also add filters to short-circuit queries.
    Current status: needs contributors.

Please let me know in the comments if I got something wrong in this summary!

Agenda: March 24th

The next meeting will be held on Tuesday, March 24 at 16.00 CET.

Today’s agenda is rather straightforward so far:

Want to add anything to the above? Please leave a comment here or reach out on Slack.

This meeting is held in the #core-sitemaps channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-plugins, #feature-projects, #xml-sitemaps