-
Notifications
You must be signed in to change notification settings - Fork 398
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
fix: support Chrome autofill when event.key
is undefined
#1888
Conversation
👷 Deploy request for docsearch pending review.Visit the deploys page to approve it
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this for RSC or SSR purposes? looking at the types, it can't be undefined, but if this check solves it, it's not a huge deal to me
cc @francoischalifour wdyt?
chrome autocomplete in forms triggers 'keydown' but the event.key is undefined |
or it's a chrome BUG. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
scrnli_2023_5_16 20-27-03.webm |
Co-authored-by: François Chalifour <francoischalifour@users.noreply.github.com>
English is not my native language; please forgive me if I offend you in any way. |
event.key
is undefined
@powerfulyang Nope, nothing to worry about 🙂 Thanks for your contribution! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the contribution!
For anyone looking for the actual chrome issue https://issuetracker.google.com/issues/41425904 |
Closes #1887.