diff options
| author | Ben Harris <bjh21@bjh21.me.uk> | 2022-10-24 22:07:12 +0100 |
|---|---|---|
| committer | Ben Harris <bjh21@bjh21.me.uk> | 2022-10-24 22:07:12 +0100 |
| commit | 322a439d801c91cf30a208cff499b33f4a5a2123 (patch) | |
| tree | a5be1d7605d1328f554cc09d2c0ee3ed807d73a1 /pattern.c | |
| parent | c1059c07fbb77f3f697b305aa55cdcd4361faf5c (diff) | |
| download | puzzles-322a439d801c91cf30a208cff499b33f4a5a2123.zip puzzles-322a439d801c91cf30a208cff499b33f4a5a2123.tar.gz puzzles-322a439d801c91cf30a208cff499b33f4a5a2123.tar.bz2 puzzles-322a439d801c91cf30a208cff499b33f4a5a2123.tar.xz | |
js: Use KeyboardEvent.keyCode and .char only as fallbacks
KeyboardEvent.keyCode is a platform-dependent mess.
KeyboardEvent.char is better-defined, but in my browser it's always
null. KeyboardEvent.key is the right thing to use when we want to
know the semantics of a key.
This commit just re-organises the big "else if" chain in key() so
that all the tests on "key" come first. That way at least if key and
keyCode disagree, we'll use the more trustworthy one.
Diffstat (limited to 'pattern.c')
0 files changed, 0 insertions, 0 deletions