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

Rearrange items in block settings menu for improved clarity #50446

Closed
2 tasks done
richtabor opened this issue May 8, 2023 · 0 comments · Fixed by #50453
Closed
2 tasks done

Rearrange items in block settings menu for improved clarity #50446

richtabor opened this issue May 8, 2023 · 0 comments · Fixed by #50453
Assignees
Labels
[Feature] Block settings menu The block settings screen [Type] Enhancement A suggestion for improvement.

Comments

@richtabor
Copy link
Member

richtabor commented May 8, 2023

Adding this issue in support of #49271, to help further clean up and organize the Block Settings Menu. Moving these items as follows allows for the more immediate edit controls to be at the consistently at the top of the menu (with no additions), while the more secondary controls are organized below.

  • Move "Group" (and "Ungroup") above "Lock"
  • Move "Move to" and "Edit as HTML" from the first MenuGroup, into the last (currently BlockSettingsMenuControls)

Visual

CleanShot 2023-05-08 at 16 43 10

*Green represents the changes.
@richtabor richtabor added [Type] Enhancement A suggestion for improvement. [Feature] Block settings menu The block settings screen labels May 8, 2023
@github-actions github-actions bot added the [Status] In Progress Tracking issues with work in progress label May 8, 2023
@priethor priethor removed the [Status] In Progress Tracking issues with work in progress label May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Block settings menu The block settings screen [Type] Enhancement A suggestion for improvement.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants