Docs: Explicitly mention new behavior coming in WP 6.6 for block variations

[gziolo]

What?

Adds mentions about the behavior change coming in WP 6.6 for Block Variations.

Why?

WordPress 6.6 is still not released, so it will be helpful to clarify the differences between WP major versions.

How?

Updates to the documentation.

Code styling changes come from the Prettier integration, which I have always enabled in my IDE.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: gziolo <[email protected]>
Co-authored-by: fabiankaegy <[email protected]>
Co-authored-by: ockham <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[fabiankaegy]

Thanks for these updates :)

[ockham]

Thank you!

[ockham]

I added the "Backport to WP Beta/RC" label since I think we'd like these changes in 6.6, as that's what determines what will be at https://developer.wordpress.org/ IIUC.

[gziolo]

I added the "Backport to WP Beta/RC" label since I think we'd like these changes in 6.6, as that's what determines what will be at https://developer.wordpress.org/ IIUC.

Historically, we have always been using trunk to generate developer docs for the block editor. So, we can verify that in 15-20 minutes. Link:

https://developer.wordpress.org/block-editor/reference-guides/block-api/block-variations/#using-isactive

[gziolo]

The changes are already synced in the block editor handbook. Removed the label.