-
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
Try updated command palette styling #53117
Conversation
Size Change: +139 B (0%) Total Size: 1.44 MB
ℹ️ View Unchanged
|
I like this, more accessible colors, i like the search icon in the field too. Feels neater. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks much more refined to me, especially the spacing and iconography colouring.
I agree this is unnecessary when the matching term is the first word of the result. I wonder if it does add enough context to justify its inclusion when the match is not the first word? |
I agree with both @adampickering and @apeatling, this is a huge improvement. As we discussed on Slack, I do like the search icon being left aligned. It feels less jarring than if it were to the right, and aligns nicely with the rest of the icons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like an overall improvement to me. I have a couple ideas that might be considered.
First, with the removal of the mark
bolding, it seems a couple of things become cruft and could be removed:
TextHighlight
component- ruleset for the
mark
element
Second, might the border-radius
of the command items be better at 2px i.e. $radius-block-ui
like most other interactive elements? Referring to this:
gutenberg/packages/commands/src/components/style.scss
Lines 64 to 65 in e87f9d0
[cmdk-item] { | |
border-radius: $grid-unit-05; |
I think it looks good, nice and simple, any reduction in borders is nearly always good. In this case I'd love a sanity check first from @jameskoster, however, because it does remove one layer of visible categorization. Before: After: GIF, before and after: Personally I also prefer keeping the bold text to highlight the search term. For me, very often, I'll look at the search results and wonder: why is a post showing up here, I'm searching for a template! In that situation, the bold text highlighting the part of the word that is matched reminding me that even if in my mind I have a particular goal, the search box looks across all taxonomies. This is a semi-strong opinion. Which is to say I'm happy to bow out if you all agree, however I'd suggest maybe you could extract that change so we can review it separately and not hold up the other improvements. Nice work! |
+1 keeping the highlight.
The reasoning seems fine to me – no need to highlight suggestions while searching. |
Sounds good; I'll add back the bold mark styling. |
Agreed; consistency is better. ✅ |
Flaky tests detected in 59d1cf0. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5715824230
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lovely stuff, thanks for sweating the details @richtabor
@WordPress/gutenberg-design Mind leaving an official review? Thanks! 🙇 |
What?
An initial attempt to revise the command palette UI.
A couple highlights:
Testing Instructions
Screenshots or screencast
Before
After