W3C home > Mailing lists > Public > public-webapi@w3.org > August 2007

Re: Key Events internationalization

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Thu, 30 Aug 2007 13:19:48 +0200
To: "Richard Ishida" <ishida@w3.org>
Cc: <public-webapi@w3.org>, <public-i18n-core@w3.org>
Message-ID: <2v8dd3tmlilnskghrnpvhq8ntgo4v948aj@hive.bjoern.hoehrmann.de>

* Richard Ishida wrote:
>Oh.  So there is a plan to specify those? If so, how would they
>differ from the .keyIdentifier, and what is .keyIdentifier for?

The Working Group resolved to specify them, yes. But so far nobody
has been able to come up with a specification, largely because they
are not particularily interoperably or meaningfully implemented.

The .keyIdentifier attribute on KeyboardEvent objects identifies
the key associated with the event object. Without a specification
for .charCode and .keyCode, I can't really say what the difference
is.

>> Instead the appendix discusses the .keyIdentifier attribute.
>
>So were/how does the .keyIdentifier attribute get its information?

The DOM implementation is responsible for setting the attribute.
The implementation would get the necessary information from its
runtime environment. For a low-level description you might try
http://en.wikipedia.org/wiki/Computer_keyboard#How_it_works and
http://en.wikipedia.org/wiki/X_Window_core_protocol#Mappings for
a higher-level description. I am not sure what you really want to 
know here.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Thursday, 30 August 2007 11:19:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:58 GMT