Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repeat Visitor Block: use stabilized role attribute property #39924

Open
Tracked by #39818
jeherve opened this issue Oct 28, 2024 · 0 comments
Open
Tracked by #39818

Repeat Visitor Block: use stabilized role attribute property #39924

jeherve opened this issue Oct 28, 2024 · 0 comments
Labels
[Block] Repeat Visitor [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Pri] Low [Type] Janitorial

Comments

@jeherve
Copy link
Member

jeherve commented Oct 28, 2024

As of WordPress 6.7 the __experimentalRole block attribute property has been stablised as role.

This property is part of the block.json specification and can be applied to any attribute of a block to designate it as being of a particular conceptual type.

Dev note: https://make.wordpress.org/core/2024/10/20/miscellaneous-block-editor-changes-in-wordpress-6-7/#stabilized-role-property-for-block-attributes

@jeherve jeherve changed the title Repeat Visitor Block: use stabilized role attribute property ([dev note](https://make.wordpress.org/core/2024/10/20/miscellaneous-block-editor-changes-in-wordpress-6-7/#stabilized-role-property-for-block-attributes)) Repeat Visitor Block: use stabilized role attribute property Oct 28, 2024
@jeherve jeherve added [Type] Janitorial [Pri] Low [Block] Repeat Visitor [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Repeat Visitor [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Pri] Low [Type] Janitorial
Projects
None yet
Development

No branches or pull requests

1 participant