Key pressed works with more than what is listed

No clue what category to put this under, so here it is.
Just something I found out. Not sure if it's a bug, or intended. Regardless, it's useful.
Interestingly, the key " " pressed predicate works with more than just what's listed in the drop-down menu.

<key  [k V] pressed?>

The k key is a normal dropdown option, so it unsurprisingly works.

<key (join [tab] @delInput @verticalEllipsis @addInput) pressed?>

However, tab is not a normal dropdown input, but oddly enough, it does work.
Some of the ones I found are understandable, but some make no sense why they would even work.
Here's all of the button presses that I found work even though they aren't present in the dropdown:
I'll also leave what I put in the thing to get it in parenthesis.

  • All of the function keys, somehow? (f1, f2, f3, f4, etc.)
  • The delete key (delete)
  • The home key apparently? (home)
  • The end key for some reason? (end)
  • The control, or ctrl key (control)
  • The alt key (alt)
  • The shift key, which could be used for capitalization detection maybe? (shift)
  • The tab key, which was the example (tab)
  • All of the symbol keys that aren't in the dropdown, like "[", "]", ";", "_", "=", ">", etc. (Whatever the symbol is)

Here are some I found that don't work:

  • Whatever this key is called: "`"
  • And the shift form: "~"
  • None of the top row, like volume up, brightness down, etc. (Despite the function keys working?)
  • The function key itself, despite being able to see function inputs?
  • The page up key and page down key
  • The power button (And yes, I did turn my computer off testing it lol)

So yeah, do whatever with this knowledge. Just thought it was interesting and I might as well share it.
There might be some keys that are only found on other computers (mine is a windows), so if there are any that work, let me know!

Also, if you put a capital letter in the key pressed block, like

<key (join [A] @delInput @verticalEllipsis @addInput) pressed?>

nothing will activate it. The normal a key won't, nor will pressing shift and a, for A. Even when case sensitivity is on, nothing activates it.

This is an intended behavior, since they don't want to fill the dropdown with every single possible key that can be detected. Plus, it's the same in scratch (except some keys are blacklisted).

Really? I didn't know it was also like that in scratch. Huh.

And it's been this way since (I think) scratch 1.4 (I know it was in scratch 2, but I don't know if it was in scratch 1.4).

Intended.

Backquote, if you're American; backtick, if you're British.

Beyond our control. Those keys are grabbed by the operating system before they can be turned into character codes.

Yeah, that's a bug. Or a misfeature, or something. Thanks. You can check for shift-A with
untitled script pic (3)

(ALL is the AND block when you drag the KEY PRESSED? block over its arrowheads rather than over one of the input slots.)

Really? I'm American, yet I've never heard of the word "backquote", I've always just called the backticks. Guess I've just grown accustomed to British English, even though I live in the US.

Maybe it's just Lispians who call it "backquote." I guess all the Americans I know are Lispians. :~P

They Work! You just need to know the name.

Really? I've always called it the grave key.

yes it does?

that's because it isn't sent to the os--it modifies other keys in the keyboard itself (unless you're using a mac (i think) keyboard)

i call it "backtick" or "grave" (usually "grave" because unicode)

But they shouldn't have called it that, because it's not an accent combiner. Although they have both ACUTE ACCENT and COMBINING ACUTE ACCENT so I guess they're being consistent. But backquote was in ASCII before there was Unicode, and that's not true for other accent characters. I think its original purpose was to be able to make ``quotes´´ in fonts with forward-slanted apostrophes.