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

FSE: The alignment option is missing from the toolbar for blocks in Site Editor #60996

Open
zdenys opened this issue Feb 10, 2022 · 2 comments
Open
Labels
Blocks Editor blocks, aka Gutenberg blocks, plugins, and extensions Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Post/Page Editor The editor for editing posts and pages. [Goal] Full Site Editing [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. [Type] Bug

Comments

@zdenys
Copy link
Contributor

zdenys commented Feb 10, 2022

Quick summary

The alignment option is missing from the toolbar for blocks in Site Editor while it's present in Post/Page Editor

Site Editor Post/Page Editor
CoverBlockSiteEditor CoverBlockPostEditor
--- ---
GroupBlockSiteEditor GroupBlockPostEditor

Steps to reproduce

  1. Create a new site at https://wordpress.com/start and you will land into the Site Editor at the end
  2. Select a block that does have an alignment option generally (such as Group, Cover, etc.)
  3. See no alignment option
  4. Create a new post/page
  5. Add a Group or Cover block

What you expected to happen

In the Site Editor I expect to see the alignment option for all blocks that do have it normally (such as Cover, group, etc.) in the post/Page editor.

What actually happened

The alignment option is missing from the toolbar for blocks in Site Editor while it's present in Post/Page Editor

Context

I previously reported this similar issue #60249

Simple, Atomic or both?

Simple

Theme-specific issue?

Tested with Zoologist theme so far.

Browser, operating system and other notes

macOS Monterrey 12.1 with Chrome 97

Reproducibility

Consistent

Severity

Some (< 50%)

Available workarounds?

No but the platform is still usable

Workaround details

No response

@zdenys zdenys added [Type] Bug [Feature] Post/Page Editor The editor for editing posts and pages. [Goal] Full Site Editing Blocks Editor blocks, aka Gutenberg blocks, plugins, and extensions User Report labels Feb 10, 2022
@zdenys zdenys added the [Pri] Normal Schedule for the next available opportuinity. label Feb 10, 2022
@kimerlin81
Copy link

Thanks @zdenys! This issue has been triaged as I was able to reproduce it (shown below).
It seems that in the Site Editor - the Cover block now shows the alignment option, but the Group block still does not:

Screen.Capture.on.2022-03-02.at.10-51-09.mp4

@kimerlin81 kimerlin81 added the Triaged To be used when issues have been triaged. label Mar 2, 2022
@Addison-Stavlo
Copy link
Contributor

Addison-Stavlo commented May 4, 2022

It seems that all top level containers directly on a template have no alignment setting and are forced as full width, while nesting the block in a top-level container (like moving the cover inside a group block) allows for the alignment setting to show up and be set.

For example, the noted 'Cover' block example above in the Site Editor. On the template level this setting is unavailable, while once this is in the context of a post and nested, the setting becomes available:

Screen Shot 2022-05-04 at 9 56 26 AM

@jeherve jeherve added Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". and removed User Report labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocks Editor blocks, aka Gutenberg blocks, plugins, and extensions Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Post/Page Editor The editor for editing posts and pages. [Goal] Full Site Editing [Pri] Normal Schedule for the next available opportuinity. Triaged To be used when issues have been triaged. [Type] Bug
Projects
None yet
Development

No branches or pull requests

4 participants