Stabilize Typography Block Supports Keys for WP 6.7

[andrewserong]

Part of:

• Tracking: Addressing Design Tooling Consistency #43241 and
• Tracking: Typography Design Tools Consistency #43242

This issues tracks progress towards stabilizing the typography block support. Note that in order to provide backwards compatibility for block plugins out in the wild, fallback support for the existing __experimental prefixes should be provided.

Stabilize the following typography block supports:

• __experimentalFontFamily → fontFamily
• __experimentalTextDecoration → textDecoration
• __experimentalFontStyle → fontStyle
• __experimentalFontWeight → fontWeight
• __experimentalLetterSpacing → letterSpacing
• __experimentalTextTransform → textTransform
• __experimentalWritingMode → writingMode

Tasks

• Update PHP block support code in lib/block-supports/typography.php to use the non __experimental prefix, falling back to the __experimental prefix if available.
• Update the JS implementations of the typography block supports to point to the non __experimental prefix, falling back to the __experimental prefix if available.
• Update the block.json schema to support the non __experimental prefix, with a note that it is only as of WP 6.7+
• Update the core blocks' block.json files to use the non __experimental prefixes
• For WP 6.7, update the supports documentation to include the new non prefixed versions.
• Once WP 6.7 is released, update the block.json schema to remove the __experimental prefix. Note that the code in WordPress should still support the __experimental prefix, but at this stage, the experimental prefix will be treated as deprecated.

In my opinion, in order to provide the widest possible support for block plugins, I think it could be valuable to provide fallback support for the __experimental in the long-term. In other words, when implementing the fallback ideas above, let's do so in a way that's easy to maintain.

[carolinan]

@scruffian I am unsure of if writingMode should be stabilized without the text orientation changes? (#60030)

[scruffian]

@scruffian I am unsure of if writingMode should be stabilized without the text orientation changes? (#60030)

I agree

[andrewserong]

Oh, thanks for flagging! I'm working on a draft PR over in #63401 — I'll omit writingMode from the stabilisation for now 👍

[ndiego]

This is a fantastic initiative @andrewserong . While we are at it, can we also tackle __experimentalBorder and __experimentalDefaultControls? I am happy to open an issue for these, but didn't want to jump the gun if you were already planning on doing so. Just let me know either way.

[andrewserong]

I am happy to open an issue for these, but didn't want to jump the gun if you were already planning on doing so. Just let me know either way.

Thanks @ndiego, if you wouldn't mind opening an issue for those, that'd be great! My main focus right now is on the Typography support and this initial stage, so that we can contain the scope of the changes we're rolling out. But my hope is that with #63401 it should make subsequent stabilization a bit easier 🙂