W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2011

Re: keyIdentifier and key events

From: Wez <wez@chromium.org>
Date: Thu, 24 Nov 2011 09:40:32 -0800
Message-ID: <CALekkJdFq0op8oLgSG442JcUQgZPwEfDEA0foz-3ximy9iTu6g@mail.gmail.com>
To: Joćo Eiras <joaoe@opera.com>
Cc: "www-dom@w3.org" <www-dom@w3.org>
The keyIdentifier field was replaced in the spec with the "key" field,
which uses similar values to represent keys, but has different behaviour
with respect to modifier keys.

On Nov 24, 2011 5:29 AM, "Joćo Eiras" <joaoe@opera.com> wrote:

> Hi.
> I see the latest drafts of DOM 3 Events no longer have keyIdentifier in
> key events.
> Why was the feature dropped ?
> There are very important use cases that it covers, mostly related with not
> relying on magic key codes which even are different between different event
> types (keydown vs. keypress).
> Currently, content pretty much expects a set of standard key codes for the
> standard computer keyboard we use. However, this is not a reliable long
> term strategy if new keyboard like devices need new key codes or key types.
> For instance, with the rise of content for TV, there is the need to
> identify the keys on a remote (Red, Green, Blue, Yellow, Play, Pause, Stop,
> Menu, etc) and that would be far more achievable if it did not rely on
> hardware or platform specific virtual key codes. There are also people
> talking about interest in the Gamepad API and it makes sense to have
> keyIdentifier as well (A, B, Z, X, Select, Start, Circle, Square, Triangle,
> L1, R1, etc.). And there can be some overlap with the already popular media
> keys on desktop keyboard (play, pause, open email). I did see some time ago
> that the specification had the keyIdentifier values for TV remotes, but not
> anymore.
> Thank you.
Received on Friday, 25 November 2011 04:22:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:36:59 UTC