ToolsPanel: Refining the component's behaviour #34257
Comments
Good ticket, thank you. Thanks for trying the current behavior. The checkbox behavior in the ellipsis menu seems to be the primary source of confusion. Let's walk through how it could work instead:
For global styles and in the future, a user could be able to control default panels via theme.json just like themes can. In one such case, you might want to remove all controls by default on a paragraph. If you did that, the ellipsis would be replaced with a [+] icon to add controls when you need them. One small thing as well: the ellipsis is vertical in recent global styles mockups, so we should update it here as well. |
Premise: I have only been involved in the review of the To me, the main source of confusion is that the same interaction/piece of UI causes 2 separate outcomes: "visually show/hide a control", and "reset the control's value". A better solution may be to have two clearly separate pieces of UI: one for toggling visibility, and one for resetting values. We should then only worry about making it clear to the user when a hidden control has a non-default (ie. that has not been reset) value. |
What problem does this address?
Now that the new
ToolsPanel
has been merged there’s been a few questions or concerns raised about its UX.The plan has always been to iterate on its behaviour and polish the panel ahead of 5.9. This issue aims to collect comments or feedback from across several PRs, issues or channels and help focus the discussion around what improvements we wish to make.
Issues raised to date
Links to feedback / comments
Related PRs
Current panel demo
ToolsPanelDemo.mp4
Questions
cc/ @jasmussen @shaunandrews @mtias @paaljoachim @ciampo
I hope you don't mind the pings on this but thought it better to cast the net wide for early thoughts and feedback.
The text was updated successfully, but these errors were encountered: