-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Combobox triggerMode="focus" does not hide content on click away #454
Comments
Please re-open. This is still reproducible with 0.13.5 |
I've updated the stackblitz to show the repro as well |
Testing in Edge it seems like its fixed. There is a smaller flicker however. |
Are we testing the same thing? This is in Chrome latest. Repro:
Result: When hitting TAB, it blurs for a frame or two, then re-focuses on its own. Screenflick.Movie.40.webm |
You're clicking inside the boundaries of the Combobox, here's a demo with distinct backgrounds: msedge_jo1iBtEWX9.mp4The flicker isn't consistent though. |
Ah, I found the cause of the issue. Attaching a CSS animation to open/close seems to cause it. See the updated stackblitz: https://stackblitz.com/edit/github-1j1ryx-qnhe3l?file=src/routes/index.tsx,src/app.css |
I think it's worth noting that the input element does not lose focus when clicking elsewhere on the page. This is an unexpected behavior. Clicking outside twice or clicking into another focusable element will make it lose focus, however. |
Describe the bug
Setting
Combobox
to usetriggerMode="focus"
retains focus when clicking outside of the input & combobox list, making it not possible to hide the listTo Reproduce
Steps to reproduce the behavior:
https://stackblitz.com/edit/github-1j1ryx-qnhe3l?file=src%2Froutes%2Findex.tsx
triggerMode="focus"
Expected behavior
the dropdown should be hidden
Screenshots
Screenflick.Movie.36.mp4
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: