-
-
Notifications
You must be signed in to change notification settings - Fork 254
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
Accessible without Input #220
Comments
+1 Encountering a similar issue. Keyboard navigation with arrow keys does not work when input is not selected, so would make sense that it also wouldn't work when the component doesn't exist |
turns out if you have the if youre using i believe it would be useful to have this info in the readme. |
Could you please provide some simplified example? I am having trouble making it work according to your way. |
@skelawsky I added tabIndex={0} to the <Command
tabIndex={0}
className="outline-none" //hides focused outline
> |
Thanks for this solution worked really well 🥇 |
Hi! I'm building Select/MultiSelect components using cmdk (coming from shadcn/ui). I wonder whether the input is considered a required component in the command tree.
Here's an example without Input. The component cannot be focused any more without input, thus, the list cannot be controlled by keyboard any more.
https://codesandbox.io/p/sandbox/eloquent-ishizaka-2tlr9l?file=/src/App.tsx:9,30
The text was updated successfully, but these errors were encountered: