-
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
Blocks in Customizer: Block toolbar positioning #25201
Comments
As I began reading the issue my first thought was to add as you mentioned a sticky toolbar (similar to mobile). Another thought that come up is.... what if we split the toolbar in two parts. Having a top and bottom sticky toolbar. Another idea.... well this is supplementary, would be to make the Customizer sidebar resizable, so the user can make the area wider and be able to see the full toolbar. I'll add on to this comment when/if other ideas come up. |
In light of closing out #25155 I want to note that in designing this next version for the toolbar, it's necessary to think about the "three dot" menu option as right now that opens as a transparent menu. |
Apparently this has been fixed recently as now in master the toolbar is fixed to top but:
|
Blocked by #25625 |
Closing this as we will be completely rearchitecting our implementation of how blocks work in the Customiser. Also worth noting that this specific design detail came up in #26900. |
Current problem
Blocks in the Customizer show the block toolbar still attached to the block itself. This causes some difficulty selecting items in the toolbar that are beyond the width of the Customizer.
Proposed solution
In the past, I've suggested that we use the mobile web view in the Customizer – the block toolbar should stick to the top. I'm still promoting this here, but @draganescu pointed out the Customizer is narrower than most phones. This means we'll need to accommodate this narrow width when we have long block toolbars.
Mockup
Prototype
The text was updated successfully, but these errors were encountered: