6.2 Dev Note Tracking Issue

[bph]

Tracking all Dev Notes from Gutenberg plugin releases 14.2 - 15.1

Please read the information below carefully. If you have questions, connect with @bph or @zzap via Slack or comment here.

• 🗓 Deadline March 3rd, 2022

Not all developer related information needs to be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already make decision on some features if it warrants a stand-alone blog post or if the information will be part of a group post.

Stand-alone post

To streamline the process and eliminate bottlenecks, all writers of stand-alone dev notes will receive privileges on the Make Core Blog. (Please connect with @bph or @zzap, if you need access)
Instructions

- Create your note in a new post, - Save as Draft - Enable public preview - Share the link to the public preview in a comment below, as "ready for review" - "For dev notes, each one must have at least two reviewers" ([Handbook](https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/))

## Part of a group post If the information related to your PR will be part of a group post, please write the **dev note in a comment on the PR**, so it can be reviewed and, if necessary commented on, by the release docs team or a reviewer.

Before you start writing 📣 please read the handbook pages:

- ⭐️ [Writing developer notes](https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/) - ⭐️ [Style & Substance section](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#style-and-substance) of the Post & Comment Guidelines for Make Blog - ⭐️ [Documentation Style Guide](https://make.wordpress.org/docs/style-guide/) - Good for reference, when in doubt, especially when English is not your native language.

The list is incomplete. We are in the process of reviewing plugin release changelogs and add as we progress on the task.

There are two labels:
needs dev note and has dev note

If you worked on a feature/module/component that definitely needs dev note, please assign the label needs dev note If you already added the Dev Note to the make blog on draft or as comment on the PR, please label it has dev note

---

~- #46212 @ellatrix ~ not in core for 6.2

• Update last inserted block state to track multiple blocks #46885 @getdave
• Upgrade React packages to v18 #45235 @youknowriad @jsnajdr @tyxla

Navigation

• Navigation block: add location->primary to fallback nav creation for classic menus. #45976 @getdave @jffng
• Adds content locking to navigation block #44739 @draganescu

CustomCSS

• Global styles: add custom CSS panel to site editor #46141
• Global Styles: Try per block custom CSS #46571 @carolinan

InspectorControls + Split Block Tools

• Inspector Controls: Stabilize the experimental control groups #47105 @aaronrobertshaw
• Sidebar Tabs: Stabilize the block inspector tabs experiment #47045
• Sidebar: Split block tools into menu, settings, and appearance tabs #45005
• Sidebar Tabs: Use editor settings to override display #46321
• Query: Remove color block supports #46147

Experimental APIs

• Limit access to experimental APIs to WordPress codebase with a new experiments package #43386 @adamziel

WP_HTML_Tag_Processor

• WP_HTML_Tag_Processor overview issue #44410 @adamziel @dmsnell

Blocks

• Blocks: Deprecate non-string descriptions #44455 @tyxla (G) DevNote
  ~- Add anchor support for dynamic blocks #44771 @Soean ~ no in 6.2
• [Heading block] Add a wp-block-heading CSS class #42122 @adamziel
• Heading: Add block classname deprecation #46138 @adamziel

Theme.json /Appearance Tools

• Code quality check for theme.json related APIs #45171 @oandregal
• Global Styles: Elements: Add a text decoration control to link elements #45643 @scruffian
• Fluid typography: adjust font size min and max rules #45536 @ramonjd (was backport to 6.1.1. but there wasn't a dev note, unless I missed it. ) (covered by dev note for below PR)
• Fluid typography: add configurable settings for minimum font size to theme.json #42489 @ramonjd @andrewserong
• Expose before filter hook in useSettings for injecting block settings in the editor #45089 @adamziel
• Heading: Add block classname deprecation #46138 @adamziel
• Shadow: Add shadow presets and UI tools in global styles #46502 @madhusudhand

Components @ciampo @mirka

• InputControl: Allow inline styles to be applied to wrapper instead of inner input #45340
  - Storybook: Set up local visual regression testing #43393
• UnitControl: Normalize wrapper classnames by removing outer wrapper #45139
• useAnchorRef: update deprecation message #45302
• Disabled: update docs to clarify the absence of inert polyfill #45272
• Dropdown: deprecate position prop, use popoverProps instead #46865
• URLPopover: use new placement prop instead of legacy position prop #44391
• BaseControl: Deprecate bottom margin #38730
• URLInput: Deprecate bottom margin #46692 @mirka @brookewp
• Components: Bump DateTimePicker deprecated prop removal version #46006
• ColorPalette, BorderBox, BorderBoxControl: polish and DRY prop types, add default values #45463
• Remove: __experimentalHasMultipleOrigins prop from colors and gradients #46315
• Components: Add support for named arguments in the navigator components #47827
• Add parent navigation support for the navigator component #47883

Global Styles

• Global Styles: Add Style Book to Global Styles #45960 @ramonjd @andrewserong
• Add a minHeight block support under dimensions #45300 @andrewserong
• Style Engine: Add support for dimensions.minHeight property #45334 @andrewserong
• Global styles: Allow indirect properties when unfiltered_html is not allowed #46388 @andrewserong

Layout/ Templates

• Add Layout controls to children of Flex layout blocks #45364 @tellthemachines
  - Template Parts: Add an option to import widgets from the sidebars #45509 @Mamaduka UI only
• Design Tools: Add a Position block support (including sticky), decoupled from layout #46142 @andrewserong

Deprecations/Removals

• Removed: Remove small APIs marked to be removed in WP 6.2 #46106 @youknowriad
  ~ Remove the nux package #46110 @youknowriad~ not yet merged into core
• Fully remove Navigation Editor screen and associated edit-navigation package #47055 @getdave

Create Block scaffolding

• [Create Block] Allows custom keys to be generated in block.json files and package.json files #44649 @ryanwelcher (most updates were already mentioned in the 6.1 Dev Note, but it seems to be missing the `customBlockJSON' part.
• Create Block: Update templates to use APIs introduced in WP 6.1 #44185 @gziolo - (already in 6.1)

Pattern and Pattern Directory

• Pattern Directory API: Add support for pagination parameters #45293 @ryelle - not relevant
• Add: Template types to the patterns API. #45814 @jorgefilipecosta backend code only.

ServerSideRender package

• ServerSideRender: add new skipBlockSupportAttributes prop #44491 @t-hamano

[ciampo]

Just flagging that @noisysocks is on parental leave as of today, I guess that the dev note for #45960 could be written by @ramonjd or @andrewserong who also helped on that PR?

[bph]

Appreciate the flag @ciampo - I updated the ping for the PR #45960 :-)

[gziolo]

#44185 @gziolo

That were code changes that propagated what was included in the dev note for WordPress 6.1.

[t-hamano]

For some blocks with caption, a toolbar button has been added to add / remove caption. Should a Dev note be written about these UI changes as well?

• [Block Library - Video]: Add toolbar button to add/remove caption #45113
• [Block Library - Image]: Add toolbar button to add a caption #44965
• Gallery Block: Add toolbar button to add a caption #47325
• [Block Library - Audio]: Add toolbar button to add/remove caption #45112

[ntsekouras]

For some blocks with caption, a toolbar button has been added to add / remove caption. Should a Dev note be written about these UI changes as well?

I don't think a dev note is needed for these, as they are UI changes.

[bph]

Totally agree, @t-hamano + @ntsekouras - Keep the questions coming, though.

[oandregal]

@bph I've added @pbking and @mikachan for #43337 as they were the ones who implemented that feature :)

---

In the case of #45171 there's only 1 thing worth having a devnote about (I presume the performance improvements do not require a devnote?). Here's the suggested text:

wp_theme_has_theme_json

WordPress 6.2 introduces a new method called wp_theme_has_theme_json(), that returns whether the active theme or its parent has a theme.json file. The goal is to provide 3rd parties with a public API they can use to query the active theme for this information.

Being so small a note, I presume it can be published as part of a bigger one?

[bph]

@oandregal thanks for the flag, if you want to combine PRs dev notes that is a great way to serve all the details in one post. This might go well with #45089 and others round theme.json and providing extenders with ways to interact with the settings.

[oandregal]

if you want to combine PRs dev notes that is a great way to serve all the details in one post.

I don't plan to, as that's my only and single contribution, and it's quite small :) I'll let others chime in. If there's no better place, it could go as part of the "miscellaneous changes" note (example in 5.9)?

[t-hamano]

I added a "ServerSideRender Package" section and wrote a dev note to #44491.

[draganescu]

I am not sure that #44739 needs a dev note, it was more like an oversight ... @Mamaduka what do you think?

[Mamaduka]

@draganescu probably not. It's a new feature for users.

[getdave]

#46885 @getdave

This was a selector originally added in #46531 and then subsequently modified in #46885. We then decided due to its instability to make it private which I did in #47638.

As a result we don't need a dev note as it's a private API.

[getdave]

Fully remove Navigation Editor screen and associated edit-navigation package #47055 @getdave

Please see dev note here.

[andrewserong]

I guess that the dev note for #45960 could be written by @ramonjd or @andrewserong who also helped on that PR?

Thanks for the ping @ciampo! I've added a draft dev note to the PR for the Style Book here: #45960 (comment)

Update: draft dev note blog post is here: https://make.wordpress.org/core/?p=102735&preview=1&_ppp=03ed6e05f5

[andrewserong]

• Fluid typography: adjust font size min and max rules #45536 @ramonjd (was backport to 6.1.1. but there wasn't a dev note, unless I missed it. ) (covered by dev note for below PR)
• Fluid typography: add configurable settings for minimum font size to theme.json #42489 @ramonjd @andrewserong

Since Ramon isn't around, I've added a draft dev note to cover these two over in this comment: #42489 (comment)

[aaronrobertshaw]

InspectorControls + Split Block Tools

I added a draft dev note in #47045 (comment) that aims to cover all the closely related PRs under the "InspectorControls + Split Block Tools" section in this issue's description.

[adamziel]

I marked #43386 as done – it doesn't require a dev note as it's a special case of an API specifically designed not to be used by contributors. I may write a separate post about it, but not a dev note.

[andrewserong]

• Add a minHeight block support under dimensions #45300 @andrewserong
• Style Engine: Add support for dimensions.minHeight property #45334 @andrewserong

I've drafted a dev note in this comment (#45300 (comment)) to cover these PRs under the umbrella of introducing the minHeight dimensions block support

• Design Tools: Add a Position block support (including sticky), decoupled from layout #46142

I've drafted a dev note for the sticky position block support in this comment: (#46142 (comment)) — I've added a couple of "why" headings there to provide answers to some of the feedback raised so far.

[tellthemachines]

Dev note for children of flex layout blocks here!

[andrewserong]

• Global styles: Allow indirect properties when unfiltered_html is not allowed #46388 @andrewserong

Added a small draft dev note to be included in a Misc dev note in this comment: #46388 (comment)

[carolinan]

I have removed [ ] #43337 @pbking @mikachan from the list because the feature is not in 6.2.

[carolinan]

Short dev note for per-block custom CSS #46571 (comment)

[ciampo]

I made a few changes to the list of components-related PRs:

• Removed SelectControl: Add onChange, onBlur and onFocus to storybook actions #45432 from the list, as it didn't need a dev note (it's just an improvement to the Storybook controls)
• Replaced SpacingSizesControl: Remove UnitControl inline style use #45412 with UnitControl: Normalize wrapper classnames by removing outer wrapper #45139, which seemed more fitting as the PR to which apply the dev note
• Removed LinkControl: use Popover new placement prop instead of legacy position prop in README #44388, as it didn't need a dev note. Instead, I added Dropdown: deprecate position prop, use popoverProps instead #46865 to the list
• Added Components: Add support for named arguments in the navigator components #47827 and Add parent navigation support for the navigator component #47883

I then went ahead and added dev notes for all of the PRs in the updated list.

[adamziel]

I've drafted a dev note for #42122 and #46138 in a comment at [Heading block] Add a wp-block-heading CSS class

I also drafted a dev note for #45089 in a comment there.

[bph]

Thank you so much @adamziel I added the Heading block dev note to the Misc Editor post
And @ndiego drafted the dev note for #45089 on the make blog. (Thank you, Nick)

[youknowriad]

@bph I've drafted a dev note for the removed APIs here #46106 (comment) We might want to include this in a "miscellaneous editor changes" dev note.

[bph]

@ciampo Thank you so much for re-organizing the Component section of the DevNote tracking issue and writing the small snippets Dev note for each listed PR.
I put them all into a stand alone post in the Make Core Blog with your name on it. Would you please review it, just to double-check, I didn't have the copy/paste devil on my shoulder.
Please edit as you see fit.

The two deprecation items, useAnchorRef and DateTimePicker, I added the deprecation section of the Misc Editor post

[bph]

Dev Notes published for WordPress 6.2

• Introduction of Block Inspector Tabs
• Shadows in Global Styles with WordPress 6.2
• Introducing the HTML API in WordPress 6.2
• Sticky position block support
• Upgrading to React 18 and common pitfalls of concurrent mode
• Add new prop to ServerSideRender component
• Custom CSS for global styles and per block
• Minimum height dimensions block support
• Editor Components updates in WordPress 6.2
• Customize settings for any block in WordPress 6.2
• Patterns API expanded to include template_types property

Miscellaneous Editor changes in WordPress 6.2

• Fluid typography minimum font size
  -- How to use the minimum font size in your theme
• Sizing controls for flex layout children
• wp-block-heading CSS class added to every Heading block
• wp_theme_has_theme_json()
• Edit block style variations from theme.json
• Updated caching behavior for APIs to access global styles and settings.
• Retaining navigation when switching themes
• Disable Openverse category in new Media tab
• Fixed focus issue after block removal.
• Bug fix: Global Styles for admin users on multi-site
• Removal of deprecated APIs and Components
  -- Formatting prop in RichText component
  -- useAnchorRef hook not deleted in 6.3
  -- DateTimePicker deprecated prop removal postponed to 6.3
  -- Deprecate non-string descriptions
  -- Removal of the Navigation Editor screen and associated package

Huge Thank you to all who contributed to dev notes and helped to review them

If you find anything missing, please let me know so we can correct that oversight quickly, preferable before the release of 6.2 final release.

[bph]

The Field Guide for WordPress 6.2 was published March 9th at 5am UTC