I think we should give it another try by including it in our UI Events spec. I like the idea of adding the static queryKeyCap(code) API to Keyboard events. I wonder about the name though. A "key capability" doesn't sound right. Are we querying for a key's locale name? e.g., queryKeyLocaleName(code)?
From: Florian Bösch [mailto:[email protected]] Sent: Thursday, January 31, 2013 7:52 AM To: Hallvord Reiar Michaelsen Steen Cc: Gary Kacmarcik (Кошмарчик); Webapps WG Subject: Re: Re: Keyboard events for accessible RIAs and Games Note that the www-dom WG has objected to querying the localized, accessible, user-friendly, keyboard symbol on grounds that it adds more bits (or tiny fractions of bits) to the user identifyable information. Contrieved usecases and advanced handwaving where employed. This is most likely ending with A) not doing accessible, localized, user friendly things or B) doing more user unfriendly things like popping "allow ..." dialogs all over. I have forked issue B in its own thread, hopefully so that neither A or B will be necessary. On Thu, Jan 31, 2013 at 11:57 AM, Florian Bösch <[email protected]<mailto:[email protected]>> wrote: Sounds fine to me, any objections to add it to the Event Level 4 spec? On Thu, Jan 31, 2013 at 11:46 AM, Hallvord Reiar Michaelsen Steen <[email protected]<mailto:[email protected]>> wrote: > What/where would be a good place to put the API for say queryKeyCap(code) ? Given that the implementation will have a KeyboardEvent property specified on the global object (i.e. window) I'd propose window.KeyboardEvent.queryKeyCap(code) which returns a string with the symbol shown on the key. I.e. On QWERTY: KeyboardEvent.queryKeyCap('Digit2') === '2' // true On AZERTY: KeyboardEvent.queryKeyCap('Digit2') === 'é' // true etc. -- Hallvord R. M. Steen Core tester, Opera Software
