WordPress Gutenberg 22.4 Update Explained: Collaborative Editing Enabled by Default, Blocks and Editor Fully Polished

1. Version overview

The Gutenberg plugin is available in 22.4.0 and 22.4.1 on GitHub Update Log. Overall pacing is clear:

• 22.4.0 is a big release in terms of functionality and experience, with a lot of new additions and enhancements.
• 22.4.1 is a minor patch release focusing on fixing a boundary issue in the Style Engine.

1.1 Core directions for 22.4.0

You can see from the update entry that it's doing three main things:

• Collaborative editing moves from experimentation to default experience
• Continuous optimization of the usability, accessibility and rendering structure of the block library and editor
• UI component system, DataView/DataForm, toolchain is more complete, convenient for theme/plugin development.

1.2 Positioning of 22.4.1

22.4.1 There is only one "code quality" related fix, which is a typical stability patch: fixing the style engine's logic for handling missing font parameters, to avoid abnormal behavior when generating style declarations.

2. 22.4.0 new feature: collaborative editing into the default experience

The "real-time collaboration" item in the changelog is key: the collaborative editing feature went from experimental to the default Gutenberg experience.
That means:

• In the future, more users will be exposed to multiplayer collaboration capabilities more naturally in the editor
• Team content production (editing, operations, reviewing) can be more closely aligned to an "online document-based" workflow.
• For site administrators, collaboration-related process specifications are more important, such as permissions, draft flow, content locking and conflict handling

3. Block library improvements: from "working" to "smoother"

22.4.0's "block library" entries are dense, and the highlights can be summarized into several categories.

3.1 Line spacing support

Added "line spacing support" to the block library. Useful for typography sites:

• Better control of the visual rhythm of headings, paragraphs, and lists
• Themes don't have to rely on a lot of custom CSS to cover their bases.
• It's also more friendly to multilingual sites, where differences in literal densities across languages are more easily balanced out

3.2 Title level variants

The "Add title level variant" appears in the block library. It means:

• Headings are not just a semantic choice for H2/H3, but can also be applied faster with a consistent visual hierarchy
• Save time when standardizing content structure and reduce the frequency of manual font size and spacing adjustments

3.3 LinkPicker and Breadcrumb Filters

The update mentions the LinkPicker component and adds filters to the breadcrumbs navigation (block_core_breadcrumbs_items). These types of changes are more on the "extensibility" side:

• Sites that have complex navigation, jump strategies, tracking parameter rules, filters that allow you to do customization without changing the core code
• LinkPicker refinements will make "selecting a link" more consistent and less fragmented across different sections.

3.4 HtmlRenderer: cleaning up the value of redundant divs

Several updates point to the HtmlRenderer and emphasize the removal of redundant div wrappers. Don't underestimate these "invisible" changes:

• Cleaner front-end DOM, less potholes in CSS coverage
• More stable rendering structure and better compatibility with third-party styles/scripts
• Performance and maintainability are also usually more stable (especially with long pages, complex templates)

3.5 Dynamic Block Anchor Support

The block library also has entries like "Add anchor support for dynamic blocks". Critical for directories, jumps, and structuring long texts:

• Content pages could do with more reliable paragraph skipping
• It also helps with SEO readability and user retention (users get to the target paragraph faster)

4、Block editor experience: panel, input and layout more detailed

The "Block Editor" section of the changelog contains a number of points that directly affect daily operations.

4.1 autoComplete: controlling browser autocomplete

Added autoComplete property to block browser auto-completion. Common Value Points:

• Some editor input boxes don't want to be "cluttered" by the browser, which can affect the editing experience.
• More controllable UI for forms and settings to reduce false triggers.

4.2 Style variants into the tool panel

"Block inspector: update style variant design to use the tool panel" This change, the goal is usually:

• More consistent information architecture: better access to styles, settings, variants
• Complex blocks are less likely to "hide" their settings.

4.3 allowWrap: flexible layout for more control

The allowWrap option (for flexible layouts) appears in layout-related updates. It solves a common problem:

• In the past, you often had to rely on CSS to get "line breaks/non-line breaks".
• It is now more possible to control typographic rules directly in the editor, and template reuse is more stable

4.4 Visibility cues and controls

The update also mentions the addition of hidden block visibility hints to the inspector, improvements to ContentOnlyControls, and other improvements in the direction of "reducing misuse":

• Users are more likely to know why a block is not visible
• Clearer status feedback when editing

5, DataView / DataForm: background data experience continues to iterate

The "Data View" update in the changelog is very focused, indicating that the team is continuing to polish the data list/management interface capabilities.

5.1 Layout and Grouping Configurable

• Add bottom selector and style to icon layout
• Add groupBy.showLabel to control the display of group title labels.
  This will allow the data view to switch more freely between a "dense display of information" and a "fresher visualization".

5.2 Filter status saving is more like a "usable tool"

Updates like "Make sure the most recently used filter is 40" are pragmatic:

• Administrators don't have to repeatedly reset filter criteria
• Smoother workflow for data operations, content operations

5.3 Date-Time Formats and Interactive Cleanup

Directions for implementing date and time formatting, removing table row focus selection with hover action buttons, etc. are:

• Reducing distractions and improving the certainty of list operations
• Convergence of interactions from "fancy" to "efficient".

5.4 LayoutCard Carding and Field Color Matching

Adjustment of DataForm's LayoutCard to card layout and updating colors of DataViews list fields are "readability engineering":

• Easier to scan
• Better suited for complex field, multi-state back-office scenarios

6, development and maintenance layer enhancement: component system and style base more mature

22.4.0 has a large number of UI components and engineering entries in Enhancements:

• Add Field, Input, Fieldset, Icon, Button and other basic components.
• Manage style variables with @wordpress/base-styles to reduce duplicate declarations across packages
• Stylelint adds design token checking
• Theme_JSON_Resolver, wp-env, Storybook and others have also been updated!
  These kinds of changes are important to developers: the more unified the components are, the more stable cross-project reuse is and the lower the maintenance costs.

7. 22.4.1 Fixed point: more stable style engine

The fix in 22.4.1 can be interpreted to mean that the style engine will terminate earlier in the add style declaration phase when font-related parameters are not passed in correctly, avoiding incorrect inheritance or invalid declarations and thus improving stability.

8. Upgrade suggestions: use this list before going online to go over it

• Editing experience: focus on testing line spacing, header variants, hidden block hints, link selector
• Theme styles: check if custom block styles, theme.json configurations, global style variables are affected
• Custom blocks/plugins: if you rely on specific DOM structures, focus on HtmlRenderer-related div cleanups
• Data Management Interface: Run a DataView with real data for filtering, grouping, date and time display.
• Release method: first upgrade in the test site/pre-release environment, and then go live in a small amount of traffic, to ensure that rollback is possible

summarize

Gutenberg 22.4.0 is a combination of "feature implementation + experience polish + engineering refinement": collaborative editing becomes the default, block libraries are easier to use, editors are more controllable, and DataView looks more like a mature backend tool. 22.4.1 patches up the boundary case of the style engine with a small fix, making it more suitable for upgrading to a stable release. It's better for upgrading to the same stable release line with peace of mind.

Contact Us
Can't read the tutorial? Contact us for a free answer! Free help for personal, small business sites!	Customer Service
① Tel: 020-2206-9892
② QQ咨询：1025174874
(iii) E-mail: info@361sale.com
④ Working hours: Monday to Friday, 9:30-18:30, holidays off