Comment 5 for bug 1035381

I'm not quite sure whether going forward we need to start adding all these letters. It's a bit of a slippery slope: sure we can add "ë" and "я", but then why not add every unicode character that can be produced by any keyboard layout? What if someone comes up with a 20-layer Chinese keyboard layout? What about all the emoji buttons on mobile virtual keyboards?

Obviously, keypress events should not be used for text input, and most keyboards don't *have* these keys, so I don't really see the value of adding these event names. The new "raw buttons" in 1.9 resolve the problem nicely of being able to bind the keys in a layout-agnostic way, and get_keyboard_map() can be used to figure out how the keys are mapped for presenting the name of the key to the user.

So I'm going to mark this as Won't Fix for now, until someone can give me a really compelling argument for why we need to add more button handles.

(Although in a way, the way the bug title is worded, it *is* fixed - all keyboard buttons now do generate an event, prefixed by "raw".)