Dev Chat Summary: March 21st (4.9.5 week 7)

This post is a summary of  the latest dev chat meeting which took place on March 21st (agenda– Slack archive).

Meeting time change

Due to Spring time change, the weekly core dev chat meeting will change from next week to be 20:00 UTC and held as usual in #core on Slack.

4.9.5 planning

WordPress 4.9.5 beta as been released Tuesday, March 20th.

There is 23 already fixed tickets and 2 blessed tasks. The milestone is clear. Some bug fixes can still ship with 4.9.5 (before RC), but enhancements have to land in 4.9.6.

Release candidate is still scheduled for Tuesday, March 27th, around 23:00 UTC.

4.9.5 release following on Tuesday, April 3rd.

Updates from focus leads and component maintainers

The GDPR Compliance team continues to meet at 16:00 UTC on Wednesdays and have reached "critical mass" in #gdpr-compliance. The team have general ideas of what needs doing and how to do it. Next step would be to get more eyes on the GDPR related tickets.

Note the max-width caption revert coming in 4.9.5 (see Dev note).

Thursday, March 22 Support meeting was dedicated to plan the increase in support traffic from a forthcoming "Try Gutenberg" promo (see Trac ticket #41316).

Core editor bug scrub time shift

With the shifts in local times, we’ll adjust the weekly core editor bug scrub starting this week to be Thursdays at 16:00 UTC and held as usual in #core-editor. Our focus will continue to be on Issues in the Merge Proposal milestone so please join the weekly discussion!

#bug-scrub, #core-editor

Core editor meeting time shift

Due to timezones being timezones, the weekly core editor meeting will change from next week to be 13:00 UTC and held as usual in #core-editor on This is to adjust for those places that spring forward this time of the year.

WordPress 4.9.5 Beta

As mentioned in the last dev chat, WordPress 4.9.5 maintenance release is scheduled for April 3rd. 

The beta package for 4.9.5 is now ready for testing. Please help us by testing this beta to ensure 4.9.5 fixes the reported issues and doesn’t introduce any new ones.

This beta release contains 23 fixes and improvements. Release candidate sheduled for March 20th.

4.9.5 improvements & fixes

See the full list of closed tickets in Trac.

Build/Test Tools

  • #43190 – Update prefixed CSS properties in about.css

Bundled Theme

  • #43317 – Twenty Seventeen: Underline links in comments


  • #39045 – W3C Validator warning: Attribute aria-required is unnecessary for elements that have attribute required.


  • #36884 – Customizer child menus incorrectly resize the site to an incorrect minimum-width
  • #43307 – Error wp-admin > Includes > theme.php
  • #43333 – Unable to add menu item

Filesystem API

  • #43417 – Infinite loop in wp_mkdir_p with open_basedir restrictions


  • #43312 – PHP 7.2 warning in wp_kses_attr()


  • #38332 – "Cheating" message insults; needs changing
  • #42789 – Bump recommended PHP version from 7.0 -> 7.2


  • #42724 – Options Media page hides breaks on desktop
  • #42968 – Media: Grid View: new upload, file is in the wrong position in the grid until after upload is complete
  • #43123 – Default captions should NOT use max-width
  • #43201 – PHP Warning: count(): Parameter must be an array or an object that implements Countable in /wp-includes/media.php on line 1206
  • #43226 – Crop setting in thumbnails never set when uploading PDF files

Bundled plugins

  • #43555 – Keep Hello Dolly from displaying sexist text in the admin

Networks and Sites

  • #43568 – E_WARNING: sprintf(): Too few arguments. [ wp-activate.php wp-activate.php (113) ]

Rest API

  • #42948 – Backbone client sending empty string in X-WP-Nonce header by default in some cases
  • #43265 – REST API JS Client: Extend custom nonce functionality to collections
  • #43266 – REST API JavaScript Client: Support an empty string for nonce


  • #43285 – The default admin referrer policy header value block the access to media on other server in admin panel


  • #42713 – Users list does not display name if Last Name empty


  • #43216 – IXR Server Warning

#4-9-5, #beta

Dev Chat Agenda: March 21st (4.9.5 week 7)

This is the agenda for the weekly dev meeting on March 21, 2018 at 21:00 UTC / March 21, 2018 at 21:00 UTC:

  • 4.9.5 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-5, #agenda, #core, #dev-chat

GDPR Compliance Chat Agenda – March 21

Agenda proposal:

  • Right to erasure: What should the site owner be able to do? And the plugin author?
  • Other Trac tickets: Review of the other tickets
  • Open discussion

Join us on slack at 16:00 UTC.
#gdpr-compliance, #agenda

Max-width captions reverted in 4.9.5

In WordPress 4.9.0 the caption shortcode output was changed to use an inline max-width style instead of width. This change broke several existing themes and has been reverted in trunk and will be in 4.9.5, when released.

For background, the change was added via #33981 and was reverted in #43123.

Any themes that would like to maintain the behavior from 4.9.0 can do so by filtering the output of image captions like this:

function filter_caption_max_width( $output, $tag ) {
    if ( 'caption' === $tag || 'wp_caption' === $tag ) {
        $output = str_replace( 'width:', 'max-width:', $output );

    return $output;

add_filter( 'do_shortcode_tag', 'filter_caption_max_width', 10, 2 );

Dev Chat Summary: March 14th (4.9.5 week 6)

This post is a summary of  the latest dev chat meeting which took place on March 14th (agendaSlack archive).

4.9.5 Planning

Planned release schedule:

  • Beta: 03/20
  • RC: 03/27
  • Expected release date: 04/03

Beta scheduled for next Tuesday, March 20th. Beta release process planned to begin after the weekly bug scrub.

An extra bug scrub is planned on Saturday 17th at 15:00 UTC for 4.9.5 triage.


  • Some 5.0 good-first-bug labelled tickets have been moved back to 4.9.5.
  • All tickets slated in 4.9.5 that are not 100% OK before beta release process will land in future release. @pento added 4.9.6 milestone to handle this.

Release planning: Gutenberg, GDPR, serve happy and other projects

There are a couple items that would be good to ship ahead of Gutenberg's release. How can WordPress best supports getting GDPR updates out ahead of its May deadline? Similarly for other non-Gutenberg projects (e.g., serve happy, debug screen, on-boarding improvements), how can WordPress best supports getting them out ahead of Gutenberg?

Now for Gutenberg, and as discussed last week there are various "Gutentasks" that could use some "Gutenhelp":

  • Various REST API tasks that can be done now in parallel
  • Core changes
  • New endpoints and infrastructure plans
  • How would inclusion of Gutenberg/JS packages work


  • @pento: about GDPR, there may be some smaller things ready for 4.9.5, but it will probably needs a 4.9.6/7 release towards the end of April or early May to add all the bits and pieces.
  • @audrasjb: question about new files or big changes like GDPR in a minor release.
  • @pento: new files can't be added in point releases, as a general rule, but there is no problem adding features (like GDPR) in 4.9.x releases, and there won't be a 4.10 release.
  • @pento: Serve happy needs some polish, but should be ready for 4.9.5. Unfortunately, it was merged to trunk early: There was design feedback on it which wasn't implemented.
  • Discussion about design in WordPress: @pento, @afercia, other contributors & core-committers to talk about design decisions in Trac workflow and in WordPress development in general. This topic will be discussed separately of this dev chat but it seems really fundamental.
  • @Krizzy: question about some good-first-bug tickets status while Gutenberg is being developed. @melchoyce answered if it’s something small and contained, it’s good to push that forward into a point release. And as a reminder, everybody is always welcome to contribute to the discussion, even if the ticket is already marked as "claimed".
  • @aduth: inclusion of Gutenberg/JS packages was a topic of the JS meeting this week. Conversation already started in core-js slack channel.
  • @pento: There have been some small core changes for Gutenberg that have landed in trunk already, mostly REST API tweaks. That process can continue. The larger REST API changes probably won't come until around when the merge proposal comes.
  • @kadamwhite announced REST API meeting is still 17:00 UTC post-daylight-savings, so that's an hour later than last week.


  • @matveb: 2.4 of Gutenberg was released today.
  • @sergeybiryukov: question about the right time for #41316 – Introduce "try Gutenberg" callout –, or still too early.
  • @pento: 4.9.5 release being in 3 weeks is good time for the callout to be added, so it should be kept in the milestone.

Various questions

  • @benoitchantre asked if #36455 should be milestoned for 4.9.5 to prevent OPcache issues to users invited to upgrade their PHP version.
  • @mikeschroder: that particular ticket needs a new patch.

Next meeting

The next meeting will take place on March 21st, 2018 at 21:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

What’s new in Gutenberg? (14th March)

2.4 π


Continues the work done in previous releases around balancing writing flow with the ability to easily insert non-text blocks.

Writing Flow

Strengthened, tweaked, and polished underlying mechanisms for handling the writing flow in order to provide more stability and consolidation.

  • Move isTyping behaviour to a separate component.
  • Inserting a block should only shift focus to a text field, otherwise focusing the block's "focus stop".
    • Example: Inserting an image should focus the top-level placeholder.
  • Pressing backspace or enter from the block's focus stop should respectively delete or insert a subsequent paragraph block.
    • Example: Pressing enter or delete on an image placeholder.
  • Pressing down arrow from a non-text-field should proceed with a tab transition as expected.
  • Multi-selection at the last text field in a block now accounts for non-contenteditable text fields.
  • Better internal identification of text fields for writing flow transitions. Previously, if a block contained a checkbox, radio, or other non-text input tags, they would be erroneously included in the writing flow sequence.
  • Inserting paragraph block (quote, etc; those with text fields) via autocomplete should move focus to the cursor.
  • Shift-arrow from a text field engages multi-selection, but not if there are other text fields in the intended direction in the same block.
  • Cancel isTyping state when focusing non text field.
  • Improve reliability of the block click-to-clear behavior.
  • When clicking below the editor move focus to last text field — this includes creating a new provisional block if last block is not text. This is equivalent to the default block appender spanning the entire viewport height of the editable canvas.
  • Introduce same undo buffering for general text to the post title (and other post properties).
  • Allow breaking out of List block upon Enter on last empty line.
  • Address conflicts between WritingFlow's selection transitioning and nested blocks by moving selection to the block's focus handler.

Other Changes

Dev Chat Agenda: March 14th (4.9.5 week 6)

This is the agenda for the weekly dev meeting on March 14, 2018 at 21:00 UTC / March 14, 2018 at 21:00 UTC:

  • 4.9.5 planning
  • Release planning (GDPR, serve happy, debug screen, on-boarding improvements, Gutenberg)
  • Contribute with Docs handbook content
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-5, #agenda, #core, #dev-chat