WordPress 6.0 editor pending issues and blockers

[priethor]

This is a tracking issue to provide a quick overview of the editor's remaining triaged tasks and is expected to evolve in the coming weeks as the 6.0 release proceeds, in the spirit of the similar issue used in the last release cycle.

What was found in the 6.0 walk-through and what currently exists in the project board is serving as the foundation.

---

🚨 Major blocking issues

✅ All good! Nothing is blocking the next Beta release.

---

⚠️ Must-haves before RC

Specific functionalities require the following issues, but they do not block or put at risk the whole release.

• Webfonts API: Move webfonts handling to internal only (not accessible) - WP 6.0 Stopgap #40472
• Layouts: Flex layout: Wrap multiple lines as default #39651
• Block placeholders: Apply duotone filter to placeholders for Site Logo & Post Featured Image blocks #40061

---

✨ Nice to have and feature polishing - Not for 6.0 anymore as time run out 🙅

• Block transforms: Keep width settings when transforming to container blocks (row, stack, group) #40059. Punted to 6.1. TL;DR; it's not a Gutenberg bug and it needs to be addressed conceptually.
• [Site Editor] Templates and Template Parts screens - Provide a way for users to add a description to custom templates. #36664
• Group block variations: Update Group Block description to apply for variations #40062
• Multi-Select: hide grouping controls for when selecting text only blocks #40063
• Multi-selection: List View: Consider hiding some of the ellipsis menus when mass selecting #40066
• Block placeholders: Improve placeholder for Post Content block #40074
• Styles sidebar: Global Styles variations: Refining hover animation #39700
• More granular multi-entity saving options for global style changes: Site Editor: Styles doesn't offer granular saving options #29388
• Refine the global styles panel, the prominence, and placement items: Reviewing Global Styles main panel #38934
• Style variations: Add "Randomize" button #39629
• Duotone filter not rendering in some places #35331 🐛
• Elements: Add styles to the footer before the block is rendered #37728 🐛

---

Major kudos to @annezazu for helping compile this list

[kjellr]

I'd suggest we add #35331 to Nice to have and feature polishing. Duotone is applied in one of the Twenty Twenty-Two alternate styles that we plan to ship with 6.0, but it does not currently render in the site editor. We can strip it out if need be, but it would be great to have it working.

[priethor]

Thanks @kjellr, I triaged it and added to the list 💯

[gziolo]

@priethor, is there anything actionable left for WP 6.0? Should we update it to target 6.1 instead?

[priethor]

With the Webfonts API alternative merged in #40472, the only remaining high-priority issue is #40059. Considering it's a bug, I would say we are in a good place. cc @ndiego for awareness of this issue, too

At this late stage, the other nice-to-haves should be punted to 6.1.

[ndiego]

@priethor see my latest comment on #40059. This is an issue in the Twenty Twenty-Two theme. It should be addressed in the theme by the 6.0 release but is not Gutenberg specific.

[priethor]

@youknowriad also shared some insightful feedback that explains it's not a bug, but a conceptual issue; solving it holistically in the editor doesn't seem feasible for 6.0.

In any case, at this point, it doesn't seem to me that this unexpected behavior should be a blocker to shipping the new block variations in 6.0, and I'd lean towards downgrading its severity here.

Any thoughts or objections, @adamziel @gziolo @ndiego @annezazu @youknowriad ?

[annezazu]

I agree with your read and don't think this should be a blocker, especially after reading the insights from Riad (thank you, as always).

[priethor]

Thanks for the feedback; I updated the opening post with the latest status update and de-prioritized it. Let's continue the #40059-specific convo there and confirm whether it can be fixed at the theme level.

[priethor]

Let's wrap this up. The only actionable item for 6.0 at this point is bug #35331, which has been partially fixed for the Site Editor and backported but still has a few loose ends (further context here).