-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grouping a single Quote block transforms it (instead of grouping it) #58042
Comments
I can replicate with WP 6.4.2, TT4, and GB 17.5.1. Screen.Recording.2024-01-24.at.10.32.00.AM.movIf 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 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? |
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. |
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 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. |
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:
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
|
Hi folks, |
Description
When I want to put a Quote block inside of a group, I select "Group" from the dropdown it transforms the block into a group, rather than groups the block. Feels like the expected behavior (based on almost all other blocks) is to group the block, not transform it.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
group-issue.mov
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: