W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: Keyboard events for accessible RIAs and Games

From: Кошмарчик <garykac@chromium.org>
Date: Wed, 30 Jan 2013 13:28:44 -0800
Message-ID: <CAGnkXoGabdAZZqa7FC2DEGZ1sye=kiWkrKFnnu01_KU5cRhOBw@mail.gmail.com>
To: Florian Bösch <pyalot@gmail.com>
Cc: Webapps WG <public-webapps@w3.org>
I was wondering that myself...

On Wed, Jan 30, 2013 at 12:58 PM, Florian Bösch <pyalot@gmail.com> wrote:

> What/where would be a good place to put the API for say queryKeyCap(code) ?
>
>
> On Wed, Jan 30, 2013 at 9:38 PM, Florian Bösch <pyalot@gmail.com> wrote:
>
>> On Wed, Jan 30, 2013 at 9:02 PM, Gary Kacmarcik (Кошмарчик) <
>> garykac@chromium.org> wrote:
>>
>>> Yes, trying to match the current (virtual) keycap was not a direct goal,
>>> but adding the 'code' attribute makes it possible (when combined with the
>>> current layout) to calculate a keycap value.
>>>
>> I think that would probably be the most preferable solution. The code
>> would be stored (in presets, preferences etc.) and the keycap (primary
>> unmodified key display for a printable key) would be queried for a code
>> whenever it's necessary to display to a user. Let's set aside that
>> consideration for a numeric keycode (it's a minor concern anyway).
>>
>
>
Received on Wednesday, 30 January 2013 21:29:18 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT