Skip to content

Inconsistency in Image block settings if it is inside Row, Stack or Grid block. #102766

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

Open
devNigel opened this issue Apr 23, 2025 · 3 comments
Labels
3. Scrubbed / Ready Triage > 3. Scrubbed / Ready Bug [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Post/Page Editor The editor for editing posts and pages. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Type] Bug When a feature is broken and / or not performing as intended WordPress.com

Comments

@devNigel
Copy link

Context and steps to reproduce

The Image Block is resizable from block settings and by dragging on the sides by default. This also works if the Image block is inside the Group block.

However, if you change the Group block to Row, Stack or Grid block, these properties will disappear, making it difficult to customize the image block when inside it.

The issue is reproducible both on simple site and atomic site.

Steps to reproduce:

  1. On page or post editor, add Image block.
  2. Observe you can adjust image size from settings and by dragging on the corners.
  3. Add Image block in Group block, these features are still available.
  4. Convert the Group block to Row, Stack or Grid to observe that these features are no longer available.

Screen recording:

CleanShot.2025-04-23.at.07.05.20.mp4

Site owner impact

More than 60% of the total website/platform users

Severity

Minor

What other impact(s) does this issue have?

No revenue impact

If a workaround is available, please outline it here.

Move the Image block outside the Row, Stack or Grid block to resize it and then add it back.

Platform

Atomic, Simple

@devNigel devNigel added [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Post/Page Editor The editor for editing posts and pages. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Apr 23, 2025
@devNigel
Copy link
Author

User report: 9692805-zd-a8c

Copy link
Contributor

📌 REPRODUCTION RESULTS
- Tested on Simple – Replicated
- Tested on Atomic – Replicated
- Replicable outside of Dotcom – No

📌 FINDINGS/SCREENSHOTS/VIDEO
I can see the issue on Dotcom sites, both on sites with and without plugins installed:

Screen Recording 2025-04-28 at 11.53.13 AM.mov

I cannot see the issue outside of Dotcom though:

Screen Recording 2025-04-28 at 11.51.45 AM.mov

I have been checking the Gutenberg repository but haven't found an existing report yet. I don't know if it's a Gutenberg issue that's fixed in one of the recent versions, but we are currently on Gutenberg 20.6.0.

I tested with unmanaged Gutenberg 20.7.0 on a Dotcom site as well, but the issue remains:

Screen Recording 2025-04-28 at 12.12.52 PM.mov

User reported that this started happening between "11 and 2pm EST" on April 22/23, which matches with the timeline when we updated to Gutenberg 20.6.0.

At this point, I am not sure what's wrong. Leaving this on the triage queue for another review.

📌 ACTIONS
- Triaged

📌 Message to Author
Thanks for reporting.

Copy link
Contributor

I can see the issue on a non-Dotcom site with Gutenberg 20.6.0:

Screen Recording 2025-04-28 at 12.25.48 PM.mov

And with Gutenberg 20.7.0 as well:

Screen Recording 2025-04-28 at 12.27.27 PM.mov

This seems to be a Gutenberg issue and not a platform issue, so I've reported here:

@arunsathiya arunsathiya removed the Needs triage Ticket needs to be triaged label Apr 28, 2025
@arunsathiya arunsathiya added [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. 3. Scrubbed / Ready Triage > 3. Scrubbed / Ready labels Apr 28, 2025 — with Linear
@jeherve jeherve added the WordPress.com label Apr 28, 2025 — with Linear
@jeherve jeherve removed the [Product] WordPress.com All features accessible on and related to WordPress.com. label Apr 28, 2025
@jeherve jeherve added the Bug label Apr 28, 2025 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. Scrubbed / Ready Triage > 3. Scrubbed / Ready Bug [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Post/Page Editor The editor for editing posts and pages. [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Type] Bug When a feature is broken and / or not performing as intended WordPress.com
Projects
Development

No branches or pull requests

3 participants