I'm not sure what specific issues Hallvord has run into, but WebKit
implementing this property is blocked on us having a bit more confidence
that the key/char properties won't be changing. Specifically, I'd like to
see some rough resolution to the following threads:
http://lists.w3.org/Archives/Public/www-dom/2012OctDec/0010.html
http://lists.w3.org/Archives/Public/public-webapps/2012JulSep/0713.html
http://lists.w3.org/Archives/Public/www-dom/2012JulSep/0103.html
http://lists.w3.org/Archives/Public/www-dom/2012OctDec/0030.html
I'd be fine pushing the USB codes off to level 4, except it's not clear to
me that we'd want the key/char properties to stay as is if we added the USB
codes.
On Mon, Oct 29, 2012 at 2:26 PM, Travis Leithead <
travis.leithead@microsoft.com> wrote:
> Hallvord, sorry I missed your IRC comment in today’s meeting, related to
> DOM3 Events:****
>
> ** **
>
> <hallvord_> event.key is still a problem child, authors trying****
>
> to use it have been complaining both to me and on the mailing****
>
> list****
>
> ** **
>
> Could you point me to the relevant discussions? The only issues with key
> that I’ve tracked relating to the spec are regarding control key usage in
> International keyboard layouts:
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18341. ****
>
> ** **
>
> Thanks,****
>
> -Travis****
>