gt;
> *From:* gary...@google.com [mailto:gary...@google.com] *On Behalf Of *Gary
> Kacmarcik (?)
> *Sent:* Friday, November 30, 2012 6:09 PM
> *To:* Travis Leithead
> *Cc:* Hallvord Reiar Michaelsen Steen; public-webapps@w3.org
>
> *Subject:* Re: Re: Event.key complaints?
com [mailto:gary...@google.com] On Behalf Of Gary
Kacmarcik (?)
Sent: Friday, November 30, 2012 6:09 PM
To: Travis Leithead
Cc: Hallvord Reiar Michaelsen Steen; public-webapps@w3.org
Subject: Re: Re: Event.key complaints?
On Fri, Nov 30, 2012 at 4:29 PM, Travis Leithead
mailto:travis.leith...@micro
On Fri, Nov 30, 2012 at 4:29 PM, Travis Leithead <
travis.leith...@microsoft.com> wrote:
> Awesome stuff Gary.
>
> ** **
>
> (And I like that we won't need to change the behavior of key or char in
> your proposal—that part made me really nervous, since IE has shipped this
> stuff since 9, and
acmarcik (?)
Sent: Friday, November 30, 2012 2:11 PM
To: Hallvord Reiar Michaelsen Steen; public-webapps@w3.org
Subject: Re: Re: Event.key complaints?
On Thu, Nov 8, 2012 at 6:37 AM, Hallvord Reiar Michaelsen Steen wrote:
>>> Hence, what I think would be most usable in the real wor
On Thu, Nov 8, 2012 at 6:37 AM, Hallvord Reiar Michaelsen Steen wrote:
>
>>> Hence, what I think would be most usable in the real world would be
>>> making event.key a mapping back to un-shifted character values of a
>>> normal QUERTY (en-US) layout. Authors are asking for stable reference
>>> val
I wrote:
>> Hence, what I think would be most usable in the real world would be
>> making event.key a mapping back to un-shifted character values of a
>> normal QUERTY (en-US) layout. Authors are asking for stable reference
>> values for identifying keys, and that's the most stable and widely
>>
On Thu 1 Nov 2012, Hallvord R. M. Steen wrote:
> I would like the "story" of event.char and event.key to be that
> event.char describes the generated character (if any) in its
> shifted/unshifted/modified/localized glory while event.key describes
> the key (perhaps on a best-effort basis, but in a
quick check in the latest
>> Firefox/Chrome stable branches and couldn't detect it, but wanted to be
>> sure.
>>
>> > -Original Message-
>> > From: Hallvord R. M. Steen [mailto:hallv...@opera.com]
>> > Sent: Thursday, November 1, 2012 1:37 PM
> > Sent: Thursday, November 1, 2012 1:37 PM
> > To: Ojan Vafai
> > Cc: Travis Leithead; public-weba...@w3c.org
> > Subject: Re: Event.key complaints?
> >
> > Travis wrote:
> >
> > >> Hallvord, sorry I missed your IRC comment in today
nches and couldn't detect it, but wanted to be sure.
> -Original Message-
> From: Hallvord R. M. Steen [mailto:hallv...@opera.com]
> Sent: Thursday, November 1, 2012 1:37 PM
> To: Ojan Vafai
> Cc: Travis Leithead; public-weba...@w3c.org
> Subject: Re: Event.k
Travis wrote:
Hallvord, sorry I missed your IRC comment in today's meeting, related to
DOM3 Events:
** **
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 d
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/Pub
Hallvord, sorry I missed your IRC comment in today's meeting, related to DOM3
Events:
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 th
13 matches
Mail list logo
