-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Tools menu styling adjustment suggestions #19447
Comments
The alignment looks good on my live site. The icon angles cause a visual weirdness, but everything is aligned correctly. Maybe this is a local build issue, @karmatosed ? I have this problem on my local |
@mapk it now is fine for me having reset my entire wp-env. I still find the hover weird though. |
@mapk @karmatosed I'd love to see keyboard shortcuts inline on the modes for clarity like they are in the Main Menu, then use the description to describe more why instead of how Maybe the keyboard shortcut is only shown for the tool(s) available to be toggled to? |
Hey @0aveRyan — you probably found a regression there, I could swear those keyboard shortcuts used to be visible, or maybe I'm misremembering? I do agree, by the way, they should be present! The question is how, though — as I recall it, we showed the keyboard shortcut conditionally based on whether it worked or not. For example if you have the edit tool selected, pressing Enter will make a line-break rather than ... well, select the too you already have. Similarly, if you're using the select tool, Enter returns to edit mode, but pressing Escape again doesn't do anything. So that is to say, I wonder if we should show those keyboard shortcuts depending on which mode you are in. |
@jasmussen yep I went back and edited that comment because I realized As you indicated, showing keyboard shortcuts only for inactive navigation tools seems a good solution. EDIT: Also, just poked through history and didn't see shortcuts in the code history, but perhaps they were there in a design mock? I'd be happy to open a PR once there's some consensus on design refinements |
Very possibly just a design mock that I'm remembering! If you'd like to open that PR, I'll help shepard it through. Go forth and conquer! |
@jasmussen I've started some of this in #21497, however something I wanted to bring up. When a Block is selected, using Neither of the shortcuts are very "global" shortcuts... if a user is in an input or textarea in the sidebar and types enter, the tool doesn't toggle either. I like the simplicity and predictability of the shortcuts... I'm not crazy about subsituting in a combo shortcut. But also now wondering whether they should be shown on the menu items. Thoughts? |
That is a doozy, and this is possibly why we ended up never adding those keyboard shortcuts in the first place. I'm skeptical now also. After all, when you see this: in that particular moment, ⌘B does indeed make the text bold. Whereas neither enter nor escape work as suggested when you read that text. Perhaps we should course correct and instead add to this sheet instead? We could add some items under "Block shortcuts". Or add a new section. What do you think? |
@jasmussen Doozy indeed 😎 A few thoughts based on your comments:
Which brings me to...
|
Yep. Let's not do that then. We can always revisit if we come around to it again.
I think this is an idea that could potentially work, but with "only two tools" it feels like a little much at this point, which seques into my answer to your next one ...
Key question to ask, and I do feel it is very important. Because it's more than just a tools selector, it is also a editing mode indicator, and this aspect is much much more important, and in fact one of the key factors in adding the item there in the first place. Selection mode, or the select tool, or navigation mode, it's had many names — this is the interface where you can press tab 20 times to select the 20th block in a long post. This is a key affordance for screen readers so as to avoid having to tab through endless tabstops on your journey. It has a number of additional benefits:
Key to this experience, though, is visualizing what's going on, surfacing what happens. To some users they might be confused why suddenly they click to start editing a block and it has a blue border when they expected a caret. They can click again to edit so it will probably not stump them for long. But if they are to ever discover what is actually going on, it's important we surface visually the mode indicator, same as how in Photoshop you might click the canvas to select and instead you paint — "oh, I had the paintbrush selected". I think your idea of a snackbar notification is an interesting one! And I do applaud you for asking questions that serve to reduce — more often than not I see the inverse. But I feel it does serve an important purpose. |
Our conversation here has taken quite the turn. Can we move the requests to separate issues? I'm closing this one out as being fixed. 😄
cc @jasmussen and @0aveRyan. In response to topic of the issue, I tested it recently and found no more problems. |
Given the keyboard shortcuts aren't global, they really only work in context of the cursor, any additional keyboard shortcuts we create aren't going to solve any problems here. But it was good to learn this! |
The tools menu could do with a few iterations in current version:
Suggestions:
The text was updated successfully, but these errors were encountered: