Nice work, this is what I see:

Those scrollbars, not sure why they are there. I suspect it's primarily something affecting the storybook rendering, though, so it may not need a fix.

If it does need a fix, and doing a little inspecting, I noticed that something like the following would fix it up:

.components-popover__content > div {
	width: 100%;
}

Those scrollbars, not sure why they are there. I suspect it's primarily something affecting the storybook rendering, though

Noting the same.

@andrewserong, is there an easy way to check if the scrollbars would disappear when the ToolsPanel is rendered inside the editor's sidebar?

On the other hand, I believe that @jasmussen 's suggested fix shouldn't hurt anyway.

We'd probably want that width fix to be added to the popover component directly, though, in case that's what it takes.

It appears the scrollbars is a regression in trunk as well 🙈

So it seems we need a fix. Whether slipstreamed in this one, or separately.

Thanks for reviewing @jasmussen and @ciampo, I was originally working on another branch, so didn't notice the scrollbars when I moved the change to a fresh branch from trunk.

It looks like the regression was introduced in #34378 — by reducing the padding on the div child of .components-popover__content, several other components now use negative margins that are too large. In this case, it's the .components-menu-group that sets each of the margins to negative -$grid-unit-15 instead of the now expected -$grid-unit-10. I've updated that component in this PR now, too.

@jasmussen was the goal with #34378 to update all instances of the popover content to the smaller padding? If so, we can work through the list of instances of -$grid-unit-15 and update to -$grid-unit-10 across a separate PR(s)?

is there an easy way to check if the scrollbars would disappear when the ToolsPanel is rendered inside the editor's sidebar?

Just to add, for testing scrollbars within the editor, we should be able to do that with the Dimensions control on the Group block. The Reset all button receives the padding rule from this PR:

Size Change: +59 B (0%)

Total Size: 1.04 MB

_{compressed-size-action}

@jasmussen was the goal with #34378 to update all instances of the popover content to the smaller padding? If so, we can work through the list of instances of -$grid-unit-15 and update to -$grid-unit-10 across a separate PR(s)?

Yes, my mistake, I'll spin up a PR for that now, sorry about that!

No worries, thanks for coming up with a quick fix! 🙇