[12.0.0+] normalizeEventKey error (key.toLowerCase)

[Mir0ke]

Description

Handsontable 11 was working fine.
But Handsontable 12.01 now has this issue.
There is no treatment for a nullable key.
Forcing toLowerCase is causing this error.

Steps to reproduce

1. handsontable\shortcuts\utils.mjs
2. Add handsontable to your page.
3. Add an input text field to your page.
4. Just using your mouse, click inside your input text field and select a value based in your web browser history.
5. Because no keys were used, handsontable produces this console error.

Demo

https://jsfiddle.net/handsoncode/c6rgz08x/

Your environment

• React wrapper version: 18.1.0
• Handsontable version: 12.0.1
• Browser name and version: Chrome 102
• Operating system: Windows 10

[AMBudnik]

Hi @Mir0ke

the demo does not seem to fit into the description of steps to replicate the issue. Could you please resend the demo and possibly a recording of the screen when the error pops?

[AMBudnik]

I was able to recreate the issue using this demo https://jsfiddle.net/0vadLq5j/3/

and get the following error

handsontable.full.js:100655 Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase')
    at normalizeEventKey (handsontable.full.js:100655:14)
    at onkeyup (handsontable.full.js:133333:51)

And it seems that it is a regression introduced in v12.0.0.

v11.1.0 - https://jsfiddle.net/4mo87szb/2/ works well
v12.0.0 - https://jsfiddle.net/4mo87szb/4/ broken

Thank you very much for sharing!

[note to myself: Inform Zen]

[wszymanski]

As the @AMBudnik shown, there is thrown a keyup event for some reason. It is the way how Gecko Chromium browsers works (reproduced on Chrome, Opera, Edge, not seen on Firefox). I'm not sure whether it is a desired behaviour. There should be done some research.

The Shortcut Manager catches every keyboard events and this event doesn't have event.key property set, that is why the error is thrown.

[warpech]

@Mir0ke this issue shows a red error in console (which we want to fix), but does it actually break anything for you? If yes, what is it?

[Mir0ke]

@Mir0ke this issue shows a red error in console (which we want to fix), but does it actually break anything for you? If yes, what is it?

It's not breaking anything.
Just the insistent error that's polluting the console everytime.