Bug: isInKeyRange function doesn't filter modifier/navigation keys

[Lumeriol]

This function is called in autosubmit.ts as isInKeyRange(e, 9, 40) to ignore keys in the legacy keyCode range 9–40 (Tab, Shift, arrows, etc.).

The problem: For modifier/navigation keys, e.key is a multi-character string (e.g. "Shift", "Control", "ArrowLeft"). Since e.key.length !== 1, the code falls through to 0, and 0 >= 9 is always false — so condition will be always false.

[radimvaculik]

Hi @Lumeriol, there's a fix ready in #1271. Could you test the PR branch and confirm it resolves the issue for you? Thanks!

[Lumeriol]

Yes, I can confirm that it works better now.
Except for one small detail—it also captures keys outside the 9–40 range, such as "Backspace" or "Delete", because they exceed the character limit.

So if I accidentally type an extra character and delete it, it won’t auto-submit until I type another character. Which can be a problem if I don’t want to search for another character. For example, if I’m filtering for “radimm” and delete the “m,” it won’t work anymore.

[radimvaculik]

Good catch, @Lumeriol! You're right — Backspace and Delete have e.key.length > 1, so the previous fix was incorrectly treating them the same as navigation/modifier keys and filtering them out.

I've pushed an additional fix to the PR branch that explicitly excludes Backspace and Delete from the skip logic, so they will continue to trigger autosubmit as expected.

Could you test it again? Thanks!

[Lumeriol]

@radimvaculik Yes, it looks fine now and is working perfectly. Thanks so much for fixing it.