Skip to content

UX: Adjust inconsistent spacing in search drop down #33074

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jordanvidrine
Copy link
Contributor

This PR makes the spacing consistent for different search states. Previously the hints box would increase in size when a term was entered into search.

I apply border styling to the correct stylesheet in order to have all versions of search dropdown retain consistent styling.

I also changed how padding is applied to keep it consistent.

CleanShot 2025-06-04 at 16 15 37@2x

@@ -166,6 +168,7 @@

.search-link {
padding: var(--search-result-element-padding);
font-size: var(--font-down-1);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is making all of this stuff smaller intentional?

image

image

also the "more" link

image

color: var(--primary-medium);

.tip-label {
background-color: rgb(var(--tertiary-rgb), 0.1);
margin-right: 0.25em;
padding: 2px 4px;
padding: 0 4px;
Copy link
Member

@awesomerobot awesomerobot Jun 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tips look off-center vertically to me now

before:
image

after:
image

@@ -135,7 +138,6 @@
display: flex;
flex-direction: column;
border-radius: var(--d-border-radius);
padding-top: 0.75rem;
Copy link
Member

@awesomerobot awesomerobot Jun 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this removes the space above the first result... more consistent with the welcome banner, but also doesn't look quite as nice to me, but maybe that's just my opinion

after:
image

before:
image

it also means the loading state regresses to an earlier issue where we have no space below the input while loading (easier to see this locally if you throttle your connection):

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants