Editor chat summary: 21 July, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, July 21, 2021, 02:00PM UTC on Slack. Moderated by @andraganescu.

Announcements

• WordPress 5.8 is out! Lots of thanks to everyone for their hard work! 
• Gutenberg 11.1 was released and so What’s new in Gutenberg 11.1.0 was posted today. Check it out for news about the new 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/ release.
• Curious about what’s coming? Go read What’s next in Gutenberg? Site Editing status check (Late July-August 2021) and keep an eye on the updated FSE scope issue.

Monthly Priorities & Key Project Updates

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

As the project has landed in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., there is now a new tracking issue set up for things identified by the community as great follow up work to improve on it.

Mobile Team

• Shipping: Block picker search and first iteration of the embed block will be shipping in the next release.
• In Progress: Scoping the next phase of Global Style Support work focusing on text-related styles.

Task Coordination

@ntsekouras

• Landed SegmentedControl (PR: 31937)
• I’m working on porting some more components from g2 and will make explorations for more layout integrations. Related Riad’s PR (PR: 33359)

@torounit

• I am working on refactoring HierarchicalTermSelector (PR: 33418)

@zieladam

• Kept an eye open on the .org widgets channel, explored issues like is_admin() being false in our API endpoints or admin functions not being loaded at all, proposed a bunch of PRs to address these.
• I surfaced the widgets editor problem with 414 too long request uris on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
• Debugged and fixed a non-deterministic Block moves to inactive widgets after being saved issue.
• Proposed a few small PRs to other small problems, Issue 33336, Ticket 53679, and more.

@mamaduka

• Started refactoring FlatTermSelector into a functional component and utilize core data module for fetching terms.
• While working on this discovered a few minor issues with the “Most Used Terms” component, which should be fixed now.
• Also, now users with author roles should be able to set featured images uploaded by other users.

@aristath

• Autogenerate headings anchors – PR: 30825.
• Allow enqueing multiple stylesheets per-block – PR: 32510.

@getdave

• I improved the build tooling by automatically grouping changelog items by feature when it is build on CI PR: 33229.

@ajlende

• Cropping for the site logo needs reviewers PR: 31607.
• Working on duotone enhancements we can discuss more during open floor PR: 33466.
• Related 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. fix for cover block spacing ui PR: 33560.

Open Floor

A test file was added to WP Core in 5.6.0, but added incorrectly, which means that the tests effectively were never run. I’m trying to fix that, but am now finding that 7 out of the 20 tests are failing. Raised by @jrf

We need someone with good knowledge of global styles to help figuring out if the test’s problem is on the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher or JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. side of the global styles.

@torounit surfaced issue 33589

This is probably a bug introduced by the recent work on the “select all” behavior in the block editor.

@ntsekouras surfaced a problem in PR: 1483 – It seems there will be the need for WP version check in patterns

The problem lies that patterns can have blocks with shape that is not supported in a WP version, but themes are also checked against WP version that are compatible. This isn’t the same WP version usually.

@ajlende asked if more people think it might be beneficial to have a system to that allow block supports to detect placeholder state.

General support for the idea was offered.

@mikeschroder raised PR: 32516 and asked if this direction is a good approach.

Looking forward for feedback from folks who know the rich-text package and can provide advice. Does that seem along the right lines for a fix?

#core-editor, #core-editor-summary