I can replicate with WP 6.4.2, TT4, and GB 17.5.1.

If I turn off GB 17.5.1, I can still replicate with just 6.4.2. Adding to 6.5 board and polish board as needs dev in case we can get a fix in in time.

This is intended right now and the responsible code is here.

Do you think the most common expectation for this use case is to wrap a Group around though? Personally I think it's better this way, but it's totally subjective. If we end up wanting the suggested behavior, we'd just need to remove the linked transform.

I feel like the intended behavior would make sense had I chosen Group from the "Transform to" menu:

But when selecting "Group" from the dropdown, it feels like the behavior shouldn't be to transform the block, it should be to put it inside of a group.

It would be helpful to know what other core blocks actually transform the block type when you select Group from the dropdown (not from the "Transform to" menu) to compare.

But when selecting "Group" from the dropdown, it feels like the behavior shouldn't be to transform the block, it should be to put it inside of a group.

I would agree with that. It's clear someone is taking an action to add a Group around it rather than transform from the three dot menu.

The issue here is that the two buttons(from transforms menu and from the block settings menu) are using the same mechanism to transform. What this means is we don't have an existing way to differentiate the handling between them.

Is this what we should aim for and explore a solution, or you think it's fine if we wrap the Quote in Group in both cases?

The issue here is that the two buttons(from transforms menu and from the block settings menu) are using the same mechanism to transform. What this means is we don't have an existing way to differentiate the handling between them.

That's an interesting point. In fact, the only block where the "Transform to Group" action removes the original block (and I've tested almost every block, including the Pull Quote, Media/Text, Gallery, etc) that I can find is the Cover block. In every other block I've tested (WP 6.4.2) the Transform to Group action places the block inside of a group but keeps the original.

I should clarify - for the cover block, the "Transform to Group" action transforms the cover into a group, but selecting "Group" from the kebab dropdown menu wraps it in a group - which I think is essentially the same behavior that the Quote block should have.

for the cover block, the "Transform to Group" action transforms the cover into a group, but selecting "Group" from the kebab dropdown menu wraps it in a group

That surprised me when I read it and checked again, but doesn't seem to be the case. It's true that for core blocks the ones that replace the block are Quote and Cover, but both buttons(transform menu and block settings menu) perform the same action, which is change the block type and not wrap.

So, my above comment still stands whether we would like different behavior, which would call for a new exploration and how useful it would be for other blocks too.

It's true that for core blocks the ones that replace the block are Quote and Cover, but both buttons(transform menu and block settings menu) perform the same action, which is change the block type and not wrap.

Well that's interesting: So if your cover block is empty/untouched, it transforms into a group, but if your cover block has a background image assigned already, it wraps the block (whether you use the transform menu or the block settings menu).

In either case I think the goal of raising this issue was to point out that the UI on this is very inconsistent and that the simplest approach (simple from the user perspective, not the dev perspective) could be:

• the Group option in the "Transform" menu would transform the block
• the Group option in the block settings menu would wrap the block

This would be applied across all blocks consistently and will be even more critical if we see #46972 merged. I think that's the behavior implied by the UI and would be happy to help with or test a PR on this if other agree that that makes sense.

Would be interested in feedback from a UI perspective as well (@richtabor)

At this stage, we're outside the ability to quickly make a decision here for 6.5. I'm going to punt it from the release as a result.

This was also reported on Trac in December 2023: https://core.trac.wordpress.org/ticket/60124

When using the Block Editor and attempting to 'group' an existing Quote block, the 'Quote' block gets converted to a 'Paragraph' block.
My expectation is that the Quote block would be grouped inside of a Group block, but instead it seems to convert the Quote block into a Group block and then has the quote content as a paragraph block within.

Hi folks,
We are only one week away from the Beta 1 cut-off date for WordPress 6.6. This issue hasn’t seen any movement in a while, so we (the editor triage leads of the 6.6 release) have decided to remove it from the WordPress 6.6 Editor Tasks project board.