The dimensions UI is displayed when the does not support Dimensions.

[shimotmk]

fix #51723

What?

Why?

Fixed a bug that caused the Dimensions panel to appear when an HTML block or shortcode block was enclosed in a group block.

How?

Testing Instructions

1. Paste the code below into the block editor.

<!-- wp:group {"layout":{"type":"flex","flexWrap":"nowrap"}} -->
<div class="wp-block-group"><!-- wp:buttons -->
<div class="wp-block-buttons"><!-- wp:button -->
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button">Button</a></div>
<!-- /wp:button --></div>
<!-- /wp:buttons -->

<!-- wp:html -->
Custom HTML
<!-- /wp:html --></div>
<!-- /wp:group -->

2. trunk branch: Click on the custom HTML block and the Dimension panel is displayed.

3. The values set in the Dimension panel are not saved and have no effect in the front end.

4. Switch to this branch and check that the Dimension panel is not visible in HTML blocks etc.

Testing Instructions for Keyboard

Screenshots or screencast

dimension.mp4

[tellthemachines]

Thanks for the PR! It's on my review list but I'm unlikely to get around to it until sometime next week 😅

[ramonjd]

This is working well for me. Nice fix!

I can't imagine any regressions given that we're checking for style block support in the style hook, but I'd feel better about a second review!

[andrewserong]

Nice fix @shimotmk!

This is testing well for me, too. At first glance, I was wondering if the check could be further down the chain in useHasChildLayout, but on second thoughts I think the approach in this PR is the right one, as it's a nice catch all for all the style components — at least one style support has to be opted into before we render any of those controls.

This LGTM, too! ✨