Block Supports: Don't merge unique attributes (ID, aria-label) in get_block_wrapper_attributes

Description

This feature is not backward compatible and creates a space in the anchor, which is not valid html.
if an anchor is set in the block editor, say "my-anchor".
if supports.anchor is set and an attribute "anchor" of type string is set in attributes in block.json
the resulting $block_wrapper_attributtes has an id of "my-anchor my-anchor"
Going back to 22.2.0 fixes the issue, but this means we cannot run the plugin for our own dynamic blocks. If there is a better way, please advise

Step-by-step reproduction instructions

in block.json set supports.anchor=true
in block.json set a string type attribute to hold the anchor
in render.php set the id of get_block_wrapper_attributes()

Screenshots, screen recording, code snippet

$block_wrapper_attributtes = get_block_wrapper_attributes(['id'=>$attributes['anchor']]);

results in

class="..." id="my-anchor my-anchor"

Environment info

WordPress 6.9.1, Gutenberg 22.5.0, 2025 theme
Most current Chrome
16-inch, 2021 M1 MBP running Tahoe 26.2

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

Please confirm which theme type you used for testing.

Block
Classic
Hybrid (e.g. classic with theme.json)
Not sure

@hadamlenz

@hadamlenz Thanks for the report.

$block_wrapper_attributtes = get_block_wrapper_attributes(['id'=>$attributes['anchor']]);

results in

class="..." id="my-anchor my-anchor"

get_block_wrapper_attributes should automatically generate the id attribute based on the anchor data, so I believe you shouldn't need to add any arguments.

Could you try the code below?

$block_wrapper_attributtes = get_block_wrapper_attributes();

I don't think ID should be included in the attributes that get concatenated with a space. if a dev sets the ID in get_block_wrapper_attributes() that should not create additional spaces. that is not valid html

$attributes[ $attribute_name ] = $extra_attributes[ $attribute_name ] . ' ' . $new_attributes[ $attribute_name ];

if the ID gets set automatically, and we are forced to use it, and we cannot manipulate it, and we cannot test for it later, you've taken away methods for developers to set the ID. this is important in places where no ID is set by an author, but some mechanism needs an ID. Again, this change is not backward compatible, so if other devs set the ID in get_block_wrapper_attributes, there will be a lot of blocks broken. This worked prior to 22.3 just fine.

I think this is a valid point. The ID (and maybe aria-label) is different from the other attributes in attributes_to_merge, as it must be unique and users might want to override it programmatically.

To maintain backward compatibility, we could update get_block_wrapper_attributes so that if it receives id, it is used instead of the native anchor.

Though I think similar blocks should also disablesupports.anchor, otherwise it will create a confusing UX.

something like this is needed

if(isset($extra_attributes["id"])){
 $attributes["id"] = $extra_attributes["id"];
} else {
 $attributes["id"] = $new_attributes["id"];
}

Thanks for the detailed explanation. Perhaps the following changes are needed in the core:

diff --git a/src/wp-includes/class-wp-block-supports.php b/src/wp-includes/class-wp-block-supports.php
index ec5bc9c8d6..3215845498 100644
--- a/src/wp-includes/class-wp-block-supports.php
+++ b/src/wp-includes/class-wp-block-supports.php
@@ -188,6 +188,21 @@ function get_block_wrapper_attributes( $extra_attributes = array() ) {
                        continue;
                }
 
+               /*
+                * The "id" and "aria-label" attributes are not space-separated
+                * lists like "class". When both block supports and the caller
+                * provide a value, always prefer the value from $extra_attributes
+                * to avoid duplicated values or unexpected concatenation.
+                */
+               if ( 'id' === $attribute_name || 'aria-label' === $attribute_name ) {
+                       if ( ! empty( $extra_attributes[ $attribute_name ] ) ) {
+                               $attributes[ $attribute_name ] = $extra_attributes[ $attribute_name ];
+                       } else {
+                               $attributes[ $attribute_name ] = $new_attributes[ $attribute_name ];
+                       }
+                       continue;
+               }
+
                if ( empty( $new_attributes[ $attribute_name ] ) ) {
                        $attributes[ $attribute_name ] = $extra_attributes[ $attribute_name ];
                        continue;

Let's aim to fix this issue in the 7.0 release.

thanks yall!

@hadamlenz

@hadamlenz, your wordpress.org username is adrock42, correct? This is to ensure that all props are listed.

Core ticket for tracking this issue: https://core.trac.wordpress.org/ticket/64603

@hadamlenz, your wordpress.org username is adrock42, correct? This is to ensure that all props are listed.

that is correct

Navigation Menu

Repository navigation

Block Supports: Don't merge unique attributes (ID, aria-label) in get_block_wrapper_attributes #75251

Description

Step-by-step reproduction instructions

Screenshots, screen recording, code snippet

Environment info

Please confirm that you have searched existing issues in the repo.

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Please confirm which theme type you used for testing.

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Block Supports: Don't merge unique attributes (ID, aria-label) in get_block_wrapper_attributes #75251

Description

Description

Step-by-step reproduction instructions

Screenshots, screen recording, code snippet

Environment info

Please confirm that you have searched existing issues in the repo.

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Please confirm which theme type you used for testing.

Activity

t-hamano commented on Feb 5, 2026

hadamlenz commented on Feb 5, 2026

hadamlenz commented on Feb 5, 2026

Mamaduka commented on Feb 5, 2026

hadamlenz commented on Feb 5, 2026

t-hamano commented on Feb 5, 2026

t-hamano commented on Feb 5, 2026

hadamlenz commented on Feb 5, 2026

t-hamano commented on Feb 5, 2026

t-hamano commented on Feb 5, 2026

hadamlenz commented on Feb 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions