Skip to content
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

Reusable blocks: block width reverts to default size when converted to reusable block #49640

Closed
worldomonation opened this issue Feb 3, 2021 · 3 comments
Labels
[Closed] Duplicate Duplicate of an existing issue. [Status] Fix Inbound Use when a fix is in unreleased component [Type] Bug When a feature is broken and / or not performing as intended

Comments

@worldomonation
Copy link
Contributor

worldomonation commented Feb 3, 2021

Steps to reproduce the behavior

  1. Create post.
  2. Insert a block that supports Full/Wide width (eg. Image block. Tiled Gallery block)
  3. Set block to Wide width.
  4. click Toolbar > Hamburger Menu > Add to Reusable Blocks

What I expected to happen

When reusable block is created, block(s) that are converted retain the width set in Step 3.

What actually happened

Turning into reusable block forces target block(s) width to revert to the default size (when inserted on editor).
These blocks do not support width wider than the default size despite Wide/Full width options being present.

Context

User scenario manual testing, back to basics.

Browser / OS version

OS: macOS Big Sur 11.1 (20C69)
Browser: Firefox Nightly 87.0a1
Browser: Safari Version 14.0.2 (16610.3.7.1.9)

Is this specific to the applied theme? Which one?

N/A

Does this happen on simple or atomic sites or both?

Both.

Is there any console output or error text?

No

Level of impact (Does it block purchases? Does it affect more than just one site?)

Minor

Screenshot / Video: If applicable, add screenshots to help explain your problem.

Screen.Recording.2021-02-02.at.4.58.52.PM.mov
Screen.Recording.2021-02-02.at.4.01.05.PM.mov
@worldomonation worldomonation added the [Type] Bug When a feature is broken and / or not performing as intended label Feb 3, 2021
@simison
Copy link
Member

simison commented Feb 3, 2021

cc @Automattic/good-mountain Gutenberg upgrade issue?

@sirreal
Copy link
Member

sirreal commented Feb 4, 2021

@WunderBart is going to investigate this.

@WunderBart
Copy link
Member

@simison @sirreal this is a known issue that is being discussed in WordPress/gutenberg#17640.

Closing in favor of WordPress/gutenberg#17640.
/cc @talldan

@sirreal sirreal added the [Status] Fix Inbound Use when a fix is in unreleased component label Feb 4, 2021
@worldomonation worldomonation added the [Closed] Duplicate Duplicate of an existing issue. label Feb 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Closed] Duplicate Duplicate of an existing issue. [Status] Fix Inbound Use when a fix is in unreleased component [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

No branches or pull requests

4 participants