-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
[Autocomplete] differentiate between hover and keyboard highlight states #33577
Conversation
5e1053f
to
c819bc2
Compare
Hi @cjtroiano. Sorry it took us so long to get to review your PR. We may need to wait until v6 before we fix it this way. Two things that come to my mind that we can do today:
cc @mnajdova for thoughts |
Agree, we should do this as part of this PR, in v6 we could make this default behavior and drop the prop.
Agree, we can anyway do this regardless of the previous implementation. Having a controlled prop for it sounds reasonable. |
Hey! Thanks @mnajdova - quick question - is there an issue that I could track when this is done? :) Right now it causes a small regression for our project. No show stopper, but it would be good to be able to see when to update the library 👍🏽 |
@einvalentin I can prioritize reviewing it if we have a contribution from the community, but I have no bandwidth to do it myself. |
I would have liked to use css for the mouse "cursor", but I wasn't able to test it properly.
If thats preferred, then I could use some help on detecting that in a test.
fix #23916