Skip to content
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

Trying to focus a text field with dropdown menu opened requires one to click twice #351

Closed
7haveeen opened this issue Feb 25, 2024 · 4 comments
Labels
closed-by-bot Issues closed by a bot. needs reproduction A reproduction is required to further investigate this issue

Comments

@7haveeen
Copy link

Describe the bug

Is the behavior intentional or a bug? When I click on the dropdown menu and then try to type in the text field with the menu open, it doesn't automatically focus on the text field. Instead, I have to click on it again for it to become active.

Reproduction

Open the input docs then click on the theme changer button at the top as if you want to change the theme, with that menu open try to focuse the input. It will require you to click twice which is not very user friendly.

Logs

No response

System Info

Windows 11

Severity

annoyance

@7haveeen 7haveeen changed the title Trying to focus a text field with dropdown menu opened require one to click twice Trying to focus a text field with dropdown menu opened requires one to click twice Feb 25, 2024
@huntabyte
Copy link
Owner

I think the issue is that the user can still interact with the input while the select is open, whereas in the original shadcn you cannot. This is likely an issue to be solved at the bits level so will transfer there.

@huntabyte huntabyte transferred this issue from huntabyte/shadcn-svelte Feb 26, 2024
@huntabyte
Copy link
Owner

Working on adding overlay elements to melt so that they can be brought here which will provide the desired behavior.

@huntabyte huntabyte added the needs reproduction A reproduction is required to further investigate this issue label Jul 9, 2024
Copy link
Contributor

github-actions bot commented Jul 9, 2024

Please provide a reproduction.

More info

Why do I need to provide a reproduction?

This project is maintained by a very small team, and we simply don't have the bandwidth to investigate issues that we can't easily replicate. Reproductions enable us to fix issues faster and more efficiently. If you care about getting your issue resolved, providing a reproduction is the best way to do that.

I've provided a reproduction - what happens now?

Once a reproduction is provided, we'll remove the needs reproduction label and review the issue to determine how to resolve it. If we can confirm it's a bug, we'll label it as such and prioritize it based on its severity.

If needs reproduction labeled issues don't receive any activity (e.g., a comment with a reproduction link), they'll be closed. Feel free to comment with a reproduction at any time and the issue will be reopened.

How can I create a reproduction?

You can use this template to create a minimal reproduction. You can also link to a GitHub repository with the reproduction.

Please ensure that the reproduction is as minimal as possible. If there is a ton of custom logic in your reproduction, it is difficult to determine if the issue is with your code or with the library. The more minimal the reproduction, the more likely it is that we'll be able to assist.

You might also find these other articles interesting and/or helpful:

Copy link
Contributor

This issue was closed because it was open for 7 days without a reproduction.

@github-actions github-actions bot added the closed-by-bot Issues closed by a bot. label Jul 17, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-by-bot Issues closed by a bot. needs reproduction A reproduction is required to further investigate this issue
Projects
None yet
Development

No branches or pull requests

2 participants