fix: support Chrome autofill when event.key is undefined

[powerfulyang]

I always encounter errors with input autocomplete when using Next.js, and it's quite frustrating.

Closes #1887.

[netlify]

👷 Deploy request for docsearch pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	e4bce7e

[shortcuts]

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?

[powerfulyang]

chrome autocomplete in forms triggers 'keydown' but the event.key is undefined

[powerfulyang]

Maybe KeyboardEvent type is incorrect.

https://www.w3.org/TR/uievents-key/#key-attr-values

or it's a chrome BUG.

paperjs/paper.js#1398
paperjs/paper.js@f1a0c0a

[francoischalifour]

Thanks!

[powerfulyang]

scrnli_2023_5_16 20-27-03.webm
the auto-filling from chrome which registers as an undefined key

[powerfulyang]

English is not my native language; please forgive me if I offend you in any way.

[francoischalifour]

@powerfulyang Nope, nothing to worry about 🙂 Thanks for your contribution!

[shortcuts]

Thanks a lot for the contribution!

[filipw01]

For anyone looking for the actual chrome issue https://issuetracker.google.com/issues/41425904