-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Style dropdown] Confusing UX in the grid of styles #11579
Comments
🤔 I though this was one of the pain points of I think it is reasonable to expect that a paragraph is not a heading — first a paragraph must be converted to a heading, then a heading style can be applied using
Proposed solution D: reduce the visual prominence/screen real estate of the unavailable styles. That way, the order remains the same, (keyboard) muscle memory remains applicable, but visual scanning is accelerated.
I think this is a premature problem to solve. Let's wait for people to run into this problem and optimize the UI for them then? |
Honestly, I'm also having second thoughts about it. On one hand, I think this would greatly improve the UX. On the other hand, this is another layer of complexity on top of what we already have. Maybe some sort of information as to why the particular style in unavailable would help? (a tooltip maybe)
This makes sense 👍 But I identified two problems with this approach:
Removing preview and changing height will create a weird layout (first row) and moving "Large paragraph" down to the next row will break the muscle memory patters. Also, this assumes that there's sorting enabled which will break the muscle memory patterns in the first place.
👍 |
I'm also cross-linking #11580 because I noticed that removing styles when multiple have been applied becomes a chore (click the dropdown, remove style A, click the dropdown, remove style B, ...).
|
FYI: this continues to be raised frequently in the |
Currently:
There are a few problems with this approach:
The text was updated successfully, but these errors were encountered: