Media Meeting Recap – January 9, 2020

Here’s a summary of the #core-media chat from January 9, 2020. Weekly media meetings happen on Thursdays at 14:00 UTC; see the full transcript here, in the Make WordPress Slack.

Attendees: @joemcgill, @karmatosed, @antpb

Upcoming Meeting Schedule

Happy 2020! Because of the holidays, the group postponed chats until Thursday, January 9.

This morning, the group also discussed moving the regular time, so more people can join the chat – particularly people working on critical tickets in the 5.4 release cycle.

Here are three options. Vote for your favorite in the comments:

  • Move the current Thursday 14:00 UTC time to 15:00 UTC
  • Move the date to Tuesday at 21:00 UTC (this option works well for the three who came to today’s meeting.)
  • Multiple meetings, to account for both sides of the world. This option would likely require a push of the currently scheduled meeting to 15:00 or 16:00 UTC as well as an agreed time and date for the second meeting. @joemcgill suggested that multiple meetings not be forced to cover the same agenda items. Some items will overlap where it makes sense, but, for example, if one meeting has cleared the ticket queue, it would be pointless for the next meeting to consist largely of a triage.

New Media ticket triage

#48194 – Unregistered image sizes used for IMG tag “srcset”

As @joemcgill pointed out: “The problem here seems to be that someone has deleted image files that are still referenced in the database in attachment metadata. Regenerating image sizes ( wp media regenerate ) would fix this problem, but should we only use registered sizes in `srcset` attributes if there are other sizes available?”

#48321 – Hotswapping featured image with gallery images

It seems the ask is for (after creating gallery) the option to click on one of the gallery items and set as featured image of the associated post. It was agreed by attendees that this may not be best fit in the gallery block UI and perhaps would be better fit as an option within the media modal when creating galleries, images, etc.

The group changed the ticket to ask for reporter feedback.

@karmatosed made another point. The “Uploaded to this post” filter, in the Set Featured Image modal, does give the reporter part of what they’re asking for.

#48325 – Additional filter in media-template.php. Let developers hide attachment page link.

@joemcgill pointed us to the code that creates the attachment link: and said, “At minimum, I think that template should check that is actually a URL before displaying [it]. [Developers] could filter the data that is used by this template.”

WordPress 5.4 Media Focuses

While it didn’t come up in the meeting, notes are a great place for all of us to develop ideas for Media focuses in 5.4.

If you have any media-related focuses you’d like to work on in the 5.4 cycle, and that you’re ready to work on, please leave a comment.

That helps the Media maintainers gather and prioritize the work. Plus, it would be great if you’d come to next week’s chat so we can all discuss your idea!

#core, #core-accessibility, #core-media, #media, #summary

What’s next in Gutenberg? (January)

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.

Block Content Areas

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

  • Work on a separate Edit Site UI
    • Load the front page template. 19081.
    • Switching templates. 19141.
  • Framework: Nest block lists from multiple entities (posts). 19203, 18739.
  • More Full Site Editing blocks (post author, post tags, site description…).
  • Expose global styles. 19255.
  • Experimental block-based theme.

Block UI

In a continuous effort to improve the accessibility and the usability of the Gutenberg design based on user feedback, an updated Block UI design is being explored. 18667.

  • Move the block movers to the block toolbar 18685.
  • Update the Block UI 19344.
  • Lighter Block DOM structure 19010.

Tightening up

Existing interactions and blocks will be iterated on:

  • Polishing the Navigation block and addressing early feedback Projects/31.
  • Expand the new Media Flow component to other blocks. 19198, 19174.
  • Block patterns for several blocks and inserter UI. 17335, 16283, 19243.

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


Editor chat summary: 08 January 2020

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, January 8, 2020, 14:00 UTC. These meetings coordinate collaboration in the development evolution of the Gutenberg project.

Gutenberg 7.2.0

The first item of the agenda is Gutenberg 7.2.0! @ella is working on the final release. The release candidate was published on Monday and is available here. It is a bigger release than usual because of the pause we had for the holidays.

The final release will contain fixes for four regressions that we caught since Monday.

Weekly Priorities

The post with the priorities for the month will be published soon and we can discuss the bigger picture in more detail in the comments when it is ready. Based on conversations we had in the past and in the general direction of the project it looks like these are the main things we should focus on during the next week:

  • FSE work (namely: separate edit UI and implement/merge additional blocks),
  • Updates to the block UI, namely the lighter block dom and the new improvements to the UI,
  • Polishing the navigation block.

Task Coordination

@karmatosed working on:

  • Navigation block triage/feedback.
  • PR 19255 Global styles designs 
  • Triage, focusing on feedback and priority labels on design issues.

@andraganescu working on:

  • starting 8 Jan 2020 all media blocks (file, video, audio, image and media+text) have the new media replace control implemented — props to @soean
  • for the next week I’ll be working on refinements to the navigation menu and other media replace control open issues
  • I could use some eyes on these two very tiny PRs:
    • PR 19504 Adding always on display of media URL
    • PR 19461  When editing a navigation link, replace the current label with the title of page or post

@gziolo working on:

  • Patterns API integration with the Inserter

@koke working on

  • PR 18055 Close to shipping Page Templates/Block Patterns
  • PR 17335 I’d like to know more about the plans for that on the web and how we can consolidate the implementations better (or at least the parts that overlap) 

@mapk working on:

  • PR 19259 Creating template variations
  • PR 19499 Moving the Welcome Guide link 
  • PR 19400 Moving the Manage reusable blocks link


  • Refocusing on Global Styles working with @karmatosed and perhaps others to get things working

@getdave working on:

  • Project 31 Focusing primarily on enhancements and fixes to the Nav Block.
  • PR 19387 UI (and accompanying REST API endpoint) to allow look-up of details about remote URLs (such as <title> tag) for display in hyperlink creation UI (LinkControl).

@retrofox working on:

  • Project 31 also on polishing the Navigation block too. As usual, we track the progress in the project board 

@bart working on: 

  • PR 18897 Navigation Block adds an empty link for untitled pages
  • PR 18321 Be consistent where we say edit or change
  • PR 18318 Navigation Block: Reduce toolbar options for menu item


  • This week — a script to automate WordPress core package updates and committed the first automatically generated package upgrade patch. I reviewed some PR’s and worked on some bugfixes (two were cherry-picked into the release).
  • Next week — Automating package updates, namely by moving the script to core. I will explore dividing the way styles are loaded in core to unblock a challenge we have on the mechanisms to simulate media queries. 
  • Reviewing PR’s and working on my current PR’s/fixes.


  • Currently focussing on lightening the block DOM and performance.

Open Floor

Adding ColorControl component

@welcher is looking for review of PR 19288 Adds ColorControl component introducing a color picker without a pallet

@jorgefilipecosta pointed out the component “PanelColorSettings” is used in core blocks. At first sight it seems this component would allow everything the new component ColorControl allows with the primary concern being this solution includes a component that core itself does not use yet.

@chrisvanpatten pointed out the main difference is that ColorControl could really be described as “ColorPickerControl” for cases where we don’t want to offer colors from a specific palette

Introduce PluginManager class

@welcher asked for input on PR 19485 Introduce PluginManager class

This PR proposes disconnecting the plugin API function calls from direct access to the low-level datatype. This intermediary makes the API more semantic, allows for future changes/updates more easily and is meant to address @youknowriad ‘s concerns about the API not being fully semantic. This PR would be a precursor to changes to the API such as #16384. Also it introduces a new filter to allow the PluginManager class to be filtered allowing for ease of testing new API features and underlying data types. This last item is not the main purpose of this PR and is easily removed.

@welcher indicated this is a larger conversation to get started as the issue of the API not being semantic enough has blocked enhancements as seen in PR 16384. @jorgefilipecosta suggested allowing time for people to review the PR asynchronously and adding discussion to a future agenda.

Cover Block Background Image Size Selector

@paaljoachim asked for design feedback on PR 19223 “Cover Block: Add Background Image Size Selector”. @karmatosed suggested and added labels so it doesn’t get passed over for review

@jorgefilipecosta noted:

  • The first issue is UI and is labeled for feedback, so it should soon be discussed/reviewed.
  • The second issue is technical the images are loaded as css property `background`. Due to limitations of CSS not having an equivalent to srcset( possible work around, the browser will always download the same image size regardless of device.

A possible fix is to use an image element but use CSS to mimic look of background as done for video backgrounds. Post comments on this solution option in Github.

@jeffreycarandang made a similar suggestion as @jorgefilipecosta  using absolute positioning <img /> instead of background-image for Cover Block which would allow responsive image sizes, noting the biggest issue to solve is the Focal Point Picker. 

Image Handling

This is a related issue to the Cover Block Background Image Selector

@azaozz Issue 6177 offers a “mini-proposal” on how to handle images in the editor and the front-end (follow-up from #4914).

Latest Post Block

@FahimMurshed Issue 13584 “Latest Posts” blocks need “pagination”/”Load more” feature.

Looking for design feedback or propose a potential design for the block.

Triage PRs

@mkaz requested self-triage because the issue count is almost 2,000 with 400+ open PRs. If you have opened an issue or PR, please confirm they are still valid. You can see your list by filtering by Author. @Jorgefilipecosta agreed and pointed out a good way to contribute is by reviewing with the added bonus that you also learn with what other people have done.

Javascript Chat Summary: Tuesday, December 17, 2019

Below is a of the discussion from this week’s JavaScript chat (agendaSlack Transcript)

Have a topic for discussion for the next meeting? Leave a suggested edit on the next chat agenda.

Next Javascript meeting is January 7th, 2020.

Because of a lot of people being AFK for their holidays we’ll skip the next two meetings.


@aduth introduce the topic by saying:

There’s been quite a bit happening this past week, both in the comments of the revisions proposal post, and in the original pull request.


Pull request: 

I think we’re in a position to make a decision on how to proceed here. From the feedback to the post, there are some general thoughts around improvements to the standard, but not any reluctance to Prettier specifically (quite the opposite, in fact!)

It would seem to me that most people are on board with this. Does anyone have any last-minute thoughts on this, or would it be fair to say we can move forward with adopting Prettier?

Based on the comments of the PR and the conversation in the chat, it seems we are in a position to merge this work.

@jsnajdr referred that the PR adds a format-js script to wp-scripts, and provides support for IDE integrations. Well-behaving Prettier editor integrations should pick up the config and the fork binary automatically.

@mkaz proposed a PR that documents these changes at

The conversation went on @jsnajdr noted that the PR does not yet format the code, but we can easily format it with `wp-scripts format-js`.

@gziolo showed availability to collaborate/discuss with @jsnajdr how format-js will operate after the PR is merged.

@gziolo noted that having prettier code formatting will alow inline snapshots on the test cases

@aduth proposed the following action items:

  1. Merge @jsnajdr‘s pull request.
  2. Review, merge @mkaz developer tools documentation.
  3. Submit standards revisions changes.

After @jsnajdr‘s pull request is merged:

  1. Create a pull request to apply formatting to the entire codebase
  2. Explore options for automated formatting.

Participants agreed on the plan.

Block Scaffolding

@gziolo shared the following GIF showing block Scaffolding working:

Block Scaffolding Tool

@gziolo managed to implement ESNext template support with wp-scripts integration and is wondering if this scaffolding mechanism should be part of the Gutenberg repository.

Participants started discussing if this solution is part of the Gutenberg repository, what will happen to the current “official” scaffolding solution offered in WP-CLI. There are technical restrictions in making something equivalent to the solution @gziolo proposed on WP-CLI because WP-CLI should not depend on node.

@gziolo will continue iterating on the new scaffolding solution and, once tested, will import it into Gutenberg.

SVGR support in wp-scripts

@mkaz started the topic by saying:

I have a PR that adds SVG support to it which is a handy addition, but not sure if we want to add it without having the same support in core Gutenberg: 

For core blocks, we don’t inline SVG, we always code them, so this mechanism would not be used by core blocks, but it may be helpful for third party block developers.

@gziolo said Parcel 2 is heading in the direction of supporting CSS and SVG imports. @aduth said Parcel faces a similar challenge, and it may be a useful reference of how to address this problem.

#core-js, #javascript, #meeting-notes

Editor chat summary: Wednesday, 18 December 2019

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, December 18, 2019, 14:00 UTC.

The agenda of the meeting is here.

Next core editor meeting is January 8th, 2020.

Because of a lot of people being AFK for their holidays we’ll skip the next two meetings and plan the next Gutenberg release (and #core-editor meeting) for January 8th, 2020.

Considering our consistent bi-weekly release schedule, there were 23 Gutenberg versions released in 2019.

Thanks to everyone who made this possible!

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.


  • I migrated the MediaReplaceFlow to the video, audio, file and media+text blocks and the PRs are waiting for a review. They’re all pretty small code wise: 19198, 19174, 19162, 19158.


  • Triage continues and trying to ensure everything has a design review on PRs within short time.
  • Wrote v1 of triage team doc and it’s up on issue.
  • Spending sometime this week clearing down queues a bit and already finding I can close some, so nice to close!
  • Began working on navigation in wp-admin: working out boundaries for this.
  • Did some mobile web testing and logged some issues, continuing this.
  • Sentence case merged.
  • Quick fix for welcome guide.
  • Lots of design feedback and testing.


  • No new development happening from me this week but I do have this open PR for deprecating wordpress/nux that I’d love some eyes on: 18981


  • I’ve been working on a few PRs to improve API and consistency for the Button component
  • I’ve been working on a keyboard shortcuts package to ultimately allow editing shortcuts and registering third party ones
  • A few janitorial PRs


  • Been doing some fixups: – Fix ArrowUp/parent block selection: 19135
  • Fix IE11 Welcome Modal: 19201
  • Would still like to land removal of “shortcuts” (needs review): 19045
  • Starting to explore user preferences persistence (more “sticky” than browser storage): 19177

Hoping to hit on a few things in next days:

  • Better data reuse for REST API _fields (opens up new optimization possibilities)
  • docgen improvements (edited) 


  • Linking Media in Media + Text block is merged! 18139
  • Was hoping for some dev help on new Block Library categories: 11406
  • If the widgets screen is ready for testing, @jorgefilipecosta, I’d like to do some usability tests.
  • Usability testing the Nav block.


  • Been working on Raw handling, RichText, and slowly making progress with the toolbar in popover PR.


  • Been working on edit-site and new entity APIs. Also template part editing flows.


  • I have one small tweak left for adding background color support to the columns block. Refactored it to use the ‘useColors’ hook. Next I’ll do the same for the Column block on a separate PR 17813


  • I’ve been working on making the editing canvas resizable, PR in progress here: 1908
  • Branching off from that, I’m starting to look at how we might optimise default block styles with CSS variables without breaking things completely in IE.

Open Floor

There was a lot of discussion on improved revision control. The main point raised by @Carike was that by using branched revisions, with minor and major designations, users will be able to use block based themes more easily. @epiqueras offered that branching or minor/major revisions are too complicated and a better improvement to revisions si to have them support block level changes.

The general agreement was that we need better revisions performance and UX.

The discussion continues in Track ticket #48953.

A second discussion happened about adding pagination to the latest posts block. There was a heated debate on whether pagination is a stand-alone block or simply a feature of blocks that need pagination. @karmatosed argued that pagination is not an option that an user might think as requireing inserting a block. @epiqueras argued pagination should be a block and be developed in such a way that if it is used standalone it would default to paginating the default post loop in the page, while other blocks might opt to use it by default (e.g. the latest posts block).

The issue is still up for debate, UX and technical solution in the GH issue #13584.

On a final note, happy holidays for those who do that and happy new year!

#meeting-notes, #core-editor, #editor, #gutenberg

Core-Privacy office hours agenda for 18 December 2019

The #core-privacy team has been having some great discussions surrounding the Consent API and Compliance Tab and will be continuing those discussions during our office hours.

Along with those discussions we would like to start planning for 5.4, so come and join us for a full office hours at our usual time this Wednesday, 18 November, at 1900 UTC in our Slack channel. All are welcome.

Our tentative agenda includes:

This will be our last office hours of 2019, Happy Holidays and see everyone tomorrow or in the next decade!!

P.S. I will be stepping down from leading these meetings in 2020 so if someone wants to take over leading meetings and writing notes come raise your hand.

#core-privacy, #privacy

WordPress 5.3.2 Release Candidate 1

WordPress 5.3.2 Release Candidate 1 (RC 1) is now available for testing!

There are two ways to test the WordPress 5.3.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the point release nightlies option), or you can download the release candidate here (zip).

What’s in this release candidate?

5.3.2 features 5 bug and regression fixes:

Here’s the full list:

  • Date/Time component: #48957 – Call to a member function format() on boolean in wp-includes/feed.php
  • Upload component: #48975 – Fix unhandled upper/lower case change in wp_unique_filename()
  • Media component: #48960 – Failed to open dir: No such file or directory in Windows
  • Build/Test tools component: #48145 – Random PHP test failures
  • Administration component: #49003 – Permalink buttons lack color contrast in most alternate color schemes

For reference, see the full 5.3.2 report on Trac.

Final release schedule

@azaozz@sergeybiryukov and @audrasjb are taking care of this maintenance release as 5.3.2 is coming very shortly after 5.3.1 was released.

Expected schedule for 5.3.2 final release is Wednesday December 18, 2019, right before or after the devchat weekly meeting

#5-3-2, #minor-releases

Dev Chat Agenda for December 18, 2019

Here is the agenda for the weekly meeting happening later today: Wednesday, December 18, 2019, at 09:00 PM UTC.


Upcoming Releases

Components Check-in

Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

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

#agenda, #core, #devchat

WordPress 5.3.2 Maintenance release schedule

Shortly after WordPress 5.3.1 was released, a couple of high severity Trac tickets were opened. The Core team immediately scheduled two bug scrubs to help these tickets moving forward.

Main tickets addressed in 5.3.2:

  • Date/Time component: #48957 – Call to a member function format() on boolean in wp-includes/feed.php
  • Upload component: #48975 – Fix unhandled upper/lower case change in wp_unique_filename()
  • Media component: #48960 – Failed to open dir: No such file or directory in Windows
  • Build/Test tools component: #48145 – Random PHP test failures
  • Administration component: #49003 – Permalink buttons lack color contrast in most alternate color schemes

For reference, see the full 5.3.2 report on Trac.

@azaozz @sergeybiryukov and @audrasjb will take care of this maintenance release as 5.3.2 is coming very shortly after 5.3.1 was released.

Expected schedule for 5.3.2:

  • Release Candidate 1: Tuesday December 17, 2019 around 20:00 UTC (start of the release process)
  • Final release: Wednesday December 18, 2019 right before or after the devchat weekly meeting

#5-3, #minor-releases

WordPress 5.3.2 – bug scrubs schedule

After WordPress 5.3.1 was released, some tickets were opened to report issues with this Security and Maintenance release. Given some issues are tagged with high severity/priority, two bug scrubs are scheduled to address them and to evaluate the need for a potential 5.3.2 Maintenance release:

Everyone is welcome to attend these meetings on Core Slack channel (requires registration).

#5-3-2, #bug-scrub