Jb Audras 7:03 am on August 31, 2021
Tags: 5.8.1 ( 4 ), 5.9 ( 7 ), core ( 313 ), week in core ( 132 )

A Week in Core – August 30, 2021

Welcome back to a new issue of Week in Core. Let’s take a look at what changed on Trac between August 23 and August 30, 2021.

33 commits
34 contributors
63 tickets created
11 tickets reopened
49 tickets closed

The Core team is currently working on the next point (5.8.1) and major (5.9) releases.

Ticket numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

Remove a misleading pointer cursor from list items in the admin menu – #51551

Build/Test Tools

Install the Composer package dependencies within the Docker environment as part of the local development environment installation and testing processes – #53945
Preserve text within backticks in Slack notifications – #52644
Remove shell: bash from PHPUnit test workflow – #53363
Remove shell: bash from code coverage workflow – #53363
Use list format when defining environment variables in Docker compose file – #53820
Remove css/dist in grunt clean command – #53719
Improve bootstrap error message for when ABSPATH folder does not exist
Move wp_list_filter() tests to their own file – #53363, #53987
Move wp_list_pluck() tests to their own file – #53363, #53987
Move wp_list_sort() tests to their own file – #53363, #53987
Remove duplicate wp_list_pluck() tests – #53363, #53987
Rename the test file and class for wp_filter_object_list() tests – #53363, #53987

Coding Standards

Add missing visibility keywords for wp_filter_object_list() and wp_list_pluck() tests – #53363, #53987
Fix WPCS issue in [51682] – #54030
Fix indentation and remove ignore annotation in wp_privacy_send_personal_data_export_email() – #53359
Make ignore annotation more specific in WP_Site_Health_Auto_Updates::test_vcs_abspath() – #53359
Remove redundant ignore annotation in populate_options() – #53359
Update the config for WordPress.PHP.FileName in PHPCS ruleset – #53359
Update the config for WordPress.PHP.NoSilencedErrors in PHPCS ruleset – #53359
Use static closures when not using $this – #53359
Pass correct default value to http_build_query() in WP_Sitemaps_Provider::get_sitemap_url() – #53635

Customize

Prevent collapsing expanded panel/section/control when Esc is pressed on a block editor instance – #54030
Respect prefers-reduced-motion media query in Customizer animations – #53542

Documentation

Add missing @since tag for the $check_signatures parameter of WP_Upgrader::run() – #53399
Clarify a comment in WP_Upgrader::run() – #53399

Editor

Ensure block attribute serialization in PHP matches the JavaScript equivalent – #53936

Filesystem API

Make sure to only call fread() on non-empty files in PclZip::privAddFile() – #54036

Media

Fix wp_unique_filename() to check for name collisions with all alternate file names when an image may be converted after uploading. This includes possible collinions with pre-existing images whose sub-sizes/thumbnails are regenerated – #53668

Menus

Save display locations for new menus – #53877

Plugins

Display a message on Plugins list table if a plugin requires a higher version of PHP or WordPress – #53990

REST API

Correct the description for the last_updated property in the block-directory endpoint – #53595

Security

Correct the inline docs for the wp_kses_allowed_html filter – #53597

Toolbar

Provide a CSS custom property for the admin bar height – #52623

Props

Thanks to the 34 people who contributed to WordPress Core on Trac last week: @jrf (10), @hellofromTonya (8), @SergeyBiryukov (6), @desrosj (5), @johnbillion (3), @dlh (2), @azaozz (2), @netweb (2), @sabernhardt (1), @pbearne (1), @swissspidy (1), @youknowriad (1), @nico23 (1), @ocean90 (1), @pbrearne (1), @timothyblynjacobs (1), @kevinfodness (1), @peterwilsoncc (1), @mikeschroder (1), @mamaduka (1), @TacoVerdo (1), @zieladam (1), @isabel_brison (1), @kevin940726 (1), @earnjam (1), @gwwar (1), @opurockey (1), @ryelle (1), @kurudrive (1), @circlecube (1), @DavidAnderson (1), @mukesh27 (1), @andraganescu (1), and @ianmjones (1).

Congrats and welcome to our 2 new contributors of the week! @kevinfodness and @kurudrive ♥️

Core committers: @sergeybiryukov (12), @hellofromtonya (7), @desrosj (5), @johnbillion (4), @peterwilsoncc (2), @mikeschroder (1), @ryelle (1), and @azaozz (1).

#5-8-1, #5-9, #core, #week-in-core

annezazu 3:23 pm on August 30, 2021
Tags: agenda ( 633 ), core-editor ( 407 ), core-editor-agenda ( 87 ), meeting ( 64 )

Editor Chat Agenda: 1 Sept 2021

Facilitator and notetaker: @annezazu

This is the agenda for the weekly editor chat scheduled for Wednesday, September 1, 2021 at 02:00 PM UTC.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

What’s new in Gutenberg (11.4). This release is planned for the day of the meeting.
Whats next in Gutenberg: July and August. If a September edition is out by the meeting time, we’ll refer to that.
Updates based on updated scope for site editing projects and WP 5.8:
- Navigation Block & Navigation Editor.
- Template editor.
- Patterns.
- Styling.
- Mobile Team.
Task Coordination.
Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
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, #core-editor, #core-editor-agenda, #meeting

Dan Farrow 11:59 am on August 29, 2021
Tags: core-css ( 171 ), summary ( 456 )

CSS Chat Summary: 26 August 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Announcements & Housekeeping

Previously we had talked about rotating the meeting facilitator on a regular basis. @notlaura asked anybody wanting to join the rota to step forward
UPDATE: We’re now working on a Meeting Guide document, which includes a facilitator schedule for people to sign up to

CSS Custom Properties (#49930)

@notlaura introduced the project for new attendees and asked for any updates
@wazeter committed two PRs last week, one in coordination with @robertg – more commits coming in a few days!
@dryanpress similarly expects to be committing in the next few days
@ryelle has updated the shared planning document with links to the PRs, and @circlecube has been helpfully indicating merged PRs by ~~striking them through~~
@ryelle asked for help reviewing the PRs – @dryanpress & @wazeter offered their assistance
@wazeter shared some details of his methodology for themes.css where he temporarily moved many custom properties to the top of the file with a prefix --wp-admin--themes
@ryelle noted that all custom properties should eventually be moved into custom-properties.css
@wazeter asked about fallback values which @ryelle responded to: hex fallback rules, which precede rules assigning rgba values for browsers that don’t understand rgba, can now be removed since core’s browser support has been updated – UPDATE: I’ve added a note about this in the shared doc
@notlaura added a final note thanking all contributions, especially newcomers

CSS Link Share / Open Floor

@notlaura raised the topic of meeting structure, in particular keeping the structured work sessions for times when attendance is low
@wazeter supported the meeting format, noting that he sometimes was unsure what to do in the structured work session
@notlaura suggested creating some general guidelines on how to run Core CSS meetings – UPDATE: Now underway here!
@ryelle volunteered to run the CSS triage session before next week’s meeting – thanks @ryelle!

Thanks everyone!

NOTE: For those interested in facilitating a future meeting or triage, please add your name to the Facilitator Schedule here

#core-css, #summary

Lara Schenck 6:29 pm on August 26, 2021
Tags: agenda ( 633 ), core-css ( 171 )

CSS Chat Agenda: August 26, 2021

The next weekly CSS meeting is Thursday, August 26 at 21:00PM UTC in the #core-css channel in Making WordPress Slack.

CSS Custom Properties (#49930)

Focused on substituting existing colors throughout Core stylesheets, the CSS Custom Properties project aims to make working with Admin Themes & Admin Color Schemes easier and more reliable both in Core and Plugins.

The #core-css team is looking for contributors interested in adopting a stylesheet (a process outlined here). No prior contributing experience is required — we’re happy to assist anyone who would like to participate! This meeting we will continue with work and collaboration, time permitting.

Meeting Agenda

Welcome (21:00PM UTC)
Announcements & Housekeeping
CSS Custom Properties (#49930)
- Overview & Updates
- How to Get Involved
- Status Check-In & Blockers
Work & Collaboration (time permitting)
Open Floor
CSS Link Share (Bring neat examples & helpful tools!)

#agenda, #core-css

Paal Joachim Romdahl 2:55 pm on August 26, 2021
Tags: core-editor ( 407 ), core-editor-summary ( 81 ), gutenberg ( 271 ), meeting notes ( 133 ), summary ( 456 )

Editor chat summary: 25 August, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, August 25, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

Gutenberg plugin releases

Gutenberg 11.3.0 release notes. Thanks to @vcanales for writing the notes and tackling the release!

New feature highlights:

New Dimensions Panel
Block inserter performance improvements
Dimension controls for Featured Image Block
New icons for Reusable Blocks and Template Parts

Gutenberg 11.4 RC is available for testing.

Whats next in Gutenberg: July and August

July and August monthly priorities.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

Check out the – Site Editor Template mosaic view

Global Styling

A proposal of an API to make blocks aware of their global styles. This API will allow the UI of a block to show their true styles by default.

Navigation Block & Navigation Editor

The team have been focused on reforming the project around the goal of removing the “experimental” status of the feature within the Gutenberg Plugin (only).
Held a Hallway Hangout on Tuesday to compare and contrast Navigation screens and determine next steps.
A summary of the meeting and decisions made is available.
Tracking issue is being updated to focus on the tasks required to remove “experimental”.
Work is continuing on exploring wider architectural issues such as how to best make use of the Navigation block whilst retaining stability.
We’ve continued with small UI/UX fixes.

Mobile

Help menu option that teaches users about the block editor
Typography controls to manipulate the font size and line height and improved color settings

In progress:

Finalizing Block Picker Search
Embed block
Editor onboarding help section
GSS Font size, line height, colors

Components squad

Working towards implementing an initial version the Global Styles Sidebar.
Color-related components: Tracking Updated ColorPicker and a proposal on next steps on a new ColorSwatch component.
Updating a set of guidelines on how to contribute to the @wordpress/components package.
Helping with the recently introduced Toolspanel component used in Dimensions Panel, and follow ups in refining component’s behavior and refactor to typescript issues.
Improvements to component’s delete the createComponent function and Rename PolymorphicComponent type to WordPress Component issues.

At the time of the meeting there were no updates on the Pattern project.

Refactored Gallery block

The refactored Gallery block main PR from October 2020 has now finally been merged, and will be included as part of Gutenberg plugin 11.4. There is also a dev note on make core.

Task Coordination

@joen

Nav block PRs, mockups around click menus and a lighter navigation editing experience.
Joen has also been reviewing a List View drag and drop improvements by Kerry.

@annezazu

Responding to Full Site Editing (FSE) feedback, testing FSE items, and helping amplify various efforts.
Working on a core editor improvement post about featured image block improvements.

@get_dave

Along with @talldanwp and @javier facilitated Navigation Editor hallway hangout.
Reorganising the Navigation Editor tracking issue.
Helping out in the Gutenberg plugin support forums.

Open Floor

@get_dave

Friendly reminder from Dave to add the most appropriate labels to PRs in GitHub, whether you’re submitting PRs or helping with triage. All efforts there make work easier for the release lead.

@paaljoachim

It would be very helpful for us who run the Core Editor Meetings to have tracking issues that are updated once a week, so we can share the project updates during the meeting. As it will also give a nice overview and it would make it easier for anyone to follow along to see the progress over time.

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

David Smith 10:01 am on August 25, 2021
Tags: feature-navigation-block-editor ( 3 ), hallwayhangout ( 2 ), navigation ( 2 ), summary ( 456 ), video ( 6 )

Hallway Hangout Summary: “compare and contrast” the Navigation screens

This post summarises the Navigation screen Hallway Hangout held on Tuesday, August 24, 2021 at 09:00 AM UTC in Zoom facilitated by @get_dave, @talldanwp and @javier.

The block-based Navigation editor screen has been behind an “experimental” feature flag within the Gutenberg plugin for some time. The purpose of the call was to outline the work required in order to remove the “experimental” status from the screen in order that the editor is active by default in the Gutenberg plugin.

The team working on the feature feel this is valuable in order to increase the visibility of the feature and therefore improve the quantity of feedback we receive.

Meeting Recording

If you’d like to watch the full recording of the session you can do so below:

Key points agreed

It was agreed that the prerequisite for removing “experimental” was: UI/UX feature parity with the existing Navigation screen (nav-menus.php) in Core.

We also acknowledged that:

We wouldn’t commit to feature parity of developer focused APIs at this stage.
Removing “experimental” in the Gutenberg plugin, would not automatically make the feature ready for merging into Core (that won’t happen until WordPress 5.9 at the earliest).

What was discussed?

The format of the hangout was an open discussion comparing and contrasting the classic menu screen with the experimental block-based navigation screen.

To this end attendees were asked to test drive both screens and note down their findings prior to the call.

The meeting facilitators also prepared a list of items as discussion points which were worked through during the call.

Each item was demonstrated, discussed and then assigned a loose priority of High/Medium/Low based on how critical the group felt the issue was to achieving feature parity.

Outcomes

The key outcomes of the call were:

A clearer understanding of the current project roadmap and the next steps required.
A list of items where the block-based Navigation Editor does not have UI/UX feature parity with the existing Navigation screen.
A rough hierarchy of task priorities from which to reprioritise the Navigation Editor tracking issue.

Next Steps

Contributors working on the Nav Editor will now look to reorganise and reprioritse the tracking issue around the problems identified during the call.

All items will be added to the tracking issue (with the possible exception of bugs).
The High priority section of the tracking issue will be reformed and refocused around the goal of “removing the experimental status from the Navigation Editor”. Only tasks directly related to this goal will be considered for inclusion in the “High” priority section.
Tasks identified during the call that were marked as Medium or High till be added to the aforementioned High priority section of the tracking issue.
Contributors will focus on tackling High priority tasks in order to realise the goal of removing the “experimental” status.

All contributors are encouraged to become involved in prioritisation. Everyone is welcome and we’d very much value your feedback. If you feel a priority is wrong or missing then please let your fellow contributors know.

Thanks to everyone who attended the hangout and we look forward to moving the Navigation Editor forward together.

#feature-navigation-block-editor, #hallwayhangout, #navigation, #summary, #video

Jonathan Desrosiers 10:03 pm on August 24, 2021
Tags: 5.8.1 ( 4 )

WordPress 5.8.x release team and 5.8.1 schedule

8/25/2021 @ 18:40 UTC: Added the “Release coordination” section to detail where release related communication will take place – @desrosj

The 5.8.x releases will follow the same consistent minor release leads strategy as the 5.7.x releases did. For the 5.8.x releases, the release leads will be:

Release Lead: @desrosj
Release Deputy: @circlecube

5.8.1 proposed schedule

The following schedule is being proposed for 5.8.1:

RC: Wednesday, September 1, 2021
Final release: Wednesday, September 8, 2021.

As of the publish date of this post, 24 tickets have already been fixed and backported to the 5.8 branch to be included in 5.8.1. 38 additional open tickets are currently in the 5.8.1 milestone for consideration. Please head over and check out that list to contribute to the release.

Release coordination

During the 5.8 release, a new, #5-8-release-leads channel was created in Slack for the release squad to have all 5.8 related conversations. Because the 5.8.x releases are part of 5.8 by extension, all coordination and conversation related to the 5.8.x releases will also be held here before the channel is archived when WordPress 5.9 is released.

Props @circlecube and @chanthaboune for peer review.

#5-8-1

Jb Audras 7:35 pm on August 24, 2021
Tags: 5.8.1 ( 4 ), 5.9 ( 7 ), core ( 313 ), week in core ( 132 )

A Week in Core – August 23, 2021

Welcome back to a new issue of Week in Core. Let’s take a look at what changed on Trac between August 16 and August 23, 2021.

27 commits
21 contributors
58 tickets created
5 tickets reopened
43 tickets closed

Pending the appointment of the WordPress 5.9 team, a number of tickets have been fixed, waiting for the next minor and major release(s).

Ticket numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.