[draganescu]

Backports the rotation block support from Gutenberg (#84505). The support is no longer behind an experiment there, and blocks opt in to it. This stays a draft until the Gutenberg PR is ready.

• src/wp-includes/block-supports/rotation.php: block types support rotation when they opt in with supports.rotation: true, and get a style attribute for it. The angle is stored in style.rotate, with viewport overrides in style['@tablet'].rotate and style['@mobile'].rotate, where 0 undoes the default rotation. Stored values are treated as untrusted: only numbers and decimal numeric strings are read, rounded to two decimals and wrapped into (-180, 180]. wp_render_rotate_support() adds the rules to the block supports stylesheet under a class generated from them, using the CSS rotate property so it combines with any transform, with viewport overrides in the theme's viewport media queries. Saved markup doesn't change.
• src/wp-includes/kses.php: adds rotate to the safe CSS properties, since the style engine filters every declaration through safecss_filter_attr().
• Tests ported from Gutenberg's phpunit/block-supports/rotation-test.php.

The supports.rotation: true opt-ins for the Image, Video, Heading and Group blocks are in their block.json files, which arrive with the package update.

Trac ticket:

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Porting the Gutenberg block support and its tests to Core naming, and writing this description. The support itself was written in Gutenberg with the same tool and reviewed by me.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

🤖 Generated with Claude Code

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.