upvote
That's keyboard code [1] vs. Keyboard key [2].

[1] Physical location of a key https://w3c.github.io/uievents/#keys-codevalues

[2] Mapping of a key https://w3c.github.io/uievents/#keys-keyvalues

The naming is terrible and I have to look it up every single time

reply
What keyboard layout are you using? I can't reproduce on a US layout.
reply
Key is Scancode 0x2B, or as a VKEY code: VK_OEM_5 (0xDC)

Javascript says the key I pressed was keycode 220 (same number as 0xDC) or key "\".

I had Tandy 1000 as the selected machine. When I look at the onscreen keyboard, I don't see a backslash key underneath backspace, but I do see one next to left shift. For keyboards that have the alternate backslash there, it is listed as having a scancode of 0x56 and a VKEY code of VK_OEM_102 (0xE2). (I haven't actually checked information specific to the actual Tandy keyboard)

reply
Yeah the OSD is only the Model F and the Tandy has some difference so the OSD keyboard may not work quite right with the Tandy.

I have to make all new pixel-art for a Tandy 1000 keyboard and PCjr keyboard. Fun

reply
Not just the OSD keyboard, my real backslash key is also pressing backspace. You can't do your classic DOS commands like "cd\" without a working backspace key.
reply
I don't think Backspace as a key was standard internationally until 1994. Apple still doesn't use it, just Delete.
reply
This is about early IBM PCs, not apple computers. And the non-working key is the Backslash key \ , not the backspace key.
reply
Old terminals had this shenanigans going on too. Backspace was not backspace and so on
reply
deleted
reply