Allow styling custom styles registered via register_block_style in theme.json

[mrleemon]

Since WP 6.2, one can style core block style variations via the "variations" key in theme.json that can be added under styles.blocks.blockname. Right now, this does not work with custom styles registered via register_block_style.

Can you add this feature, please?

[t-hamano]

@mrleemon

Thanks for the report.

Currently, #49396 has been submitted to add custom CSS to elements and variations. I believe this PR will solve your problem.

[mrleemon]

Sorry, I didn't see that PR. Thanks!

[mrleemon]

Reopening because the linked PR is about adding support for the "css" property to elements and variations, and my issue is about adding simple styling support (color, margin, padding, typography, etc.) to variations.

[t-hamano]

Regarding adding styling support to block variations, I think this was implemented in #46343. The example code can be found in this section, which is part of the WordPress 6.2 Field Guide.

[mrleemon]

Regarding adding styling support to block variations, I think this was implemented in #46343. The example code can be found in this section, which is part of the WordPress 6.2 Field Guide.

Yes, I know, but it only works for CORE styles (for example, the "rounded" style in the image block), not custom styles registered via register_block_style

[tellthemachines]

Thanks for bringing this up!

it only works for CORE styles (for example, the "rounded" style in the image block), not custom styles registered via register_block_style

Correct, the initial implementation only included core style variations, with the standard design tools. Because existing custom style variations are styled via a classic stylesheet, which depending on specificity might not be overridable with the core design tools such as color, typography etc.., custom styles were excluded then.

I'm thinking that the custom CSS field could be leveraged to solve that problem, and also that it should be possible to add new custom variations from theme.json. I opened an issue in #49602 suggesting some next steps.