W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec

From: Florian Bösch <pyalot@gmail.com>
Date: Mon, 11 Mar 2013 23:42:42 +0100
Message-ID: <CAOK8ODjdPD_xp-gqmdng1+bEYj8BEaCzNB=RqH0WS=SCOisRPg@mail.gmail.com>
To: Brad Pettit <Brad.Pettit@microsoft.com>
Cc: Wez <wez@chromium.org>, "Hallvord R. M. Steen" <hallvord@opera.com>, Masayuki Nakano <masayuki@d-toybox.com>, "www-dom@w3.org" <www-dom@w3.org>
On Mon, Mar 11, 2013 at 11:31 PM, Brad Pettit <Brad.Pettit@microsoft.com>wrote:

>  **1.      **Just because a UA incorrectly implements the keydown/keyup
> event doesn’t mean a new spec will fix the problem. Bugs in UA
> implementations of keydown/keyup and standardization of charCode can be
> fixed to the extent that it is fixable. Part of the problem is the hardware
> dependent nature of it, and have existed since DOM 0.
>
Shortcut systems aren't interested in charCodes with the exception of what
character is printed on the cap to display to a user. This information is
contained in the keyboard layout the system is using.

The specification (Event Level 4 keyboard events) *is* intended to fix a
lot of keyCode's shortcomings. And those issues aren't going to fix
themselves without anybody telling the UAs how to do it, or it would've
happend by now. Besides, keyboards *are* the most ubiquitous input devices
on the planet, and no native application in existence has to put up with
the sheer flimsyness and utter unreliability of HTMLs keyCode.


> 2.      **Usually there is no standard way for an app or browser to
> answer the question “given a text character, what key or sequence of keys
> will generate [this] character?” since it is a question the driver answers.
>
This is not a question shortcut systems are interested in.
Received on Monday, 11 March 2013 22:43:13 GMT

This archive was generated by hypermail 2.3.1 : Monday, 11 March 2013 22:43:16 GMT