Restore fuzzy search width #824
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to 199a704 in 1 minute and 3 seconds. Click for details.
- Reviewed
13lines of code in1files - Skipped
0files when reviewing. - Skipped posting
1draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. humanlayer-wui/src/components/FuzzySearchInput.tsx:286
- Draft comment:
Uncommenting the width styling (w-[var(--radix-popover-trigger-width)]) restores the intended behavior. Ensure that the CSS variable '--radix-popover-trigger-width' is defined so that the popover width adjusts correctly. - Reason this comment was not posted:
Comment looked like it was already resolved.
Workflow ID: wflow_l5yzuH4LZFsxTYHK
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
K-Mistele
approved these changes
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem(s) was I solving?
The fuzzy search dropdown used for selecting directories in the draft session launcher was rendering with an extremely narrow width, making it difficult to read and select directory paths. This affected both the working directory input field and the additional directories dropdown.
The issue was introduced in PR #798 (commit
c24f2956) when implementing directory validation and creation features. During development, the CSS class controlling the popover width (w-[var(--radix-popover-trigger-width)]) was commented out, likely for debugging purposes, but was never restored.What user-facing changes did I ship?
Fixed: The fuzzy search dropdown now correctly matches the width of its trigger input field, making directory paths fully readable when browsing and selecting directories in the draft session launcher.
Affected Components:
FuzzySearchInput/SearchInputHow I implemented it
Uncommented the CSS class
w-[var(--radix-popover-trigger-width)]inFuzzySearchInput.tsxat line 287.This Radix UI CSS variable contains the width of the popover's trigger element (the input field), and applying it ensures the dropdown matches the input width instead of defaulting to content-based width.
Technical Details:
humanlayer-wui/src/components/FuzzySearchInput.tsxPopoverContentcomponent--radix-popover-trigger-widthCSS variable is automatically provided by Radix UI's Popover componentHow to verify it
Automated Checks
bun run typecheck)bun run lint)Manual Testing
To verify the fix works:
/)Regression testing:
Description for the changelog
Fix fuzzy search dropdown width in draft session launcher - dropdown now correctly matches input field width instead of being too narrow to read directory paths