Web Applications Working Group Issue Tracker:
In the current draft of Key Identifiers, including the new algorithm
wording, there is a bias toward uppercase characters. Essentially, if
a key is pressed that gives a character codepoint which is lowercase,
for which there is an uppercase
Hi, Cameron-
CCing i18n folks; for reference, please see:
http://www.w3.org/2008/webapps/track/issues/23
Cameron McCormack wrote (on 6/29/08 3:47 AM):
Web Applications Working Group Issue Tracker:
In the current draft of Key Identifiers, including the new algorithm
wording, there is a bias
Hi Doug.
Doug Schepers:
Converting to uppercase strikes me as needless legacy from
keyCode/charCode. Is there some pragmatic reason to force this
casting?
Cameron McCormack:
These strings are meant to represent keys, rather than characters of
input.
Doug Schepers:
A reasonable argument,
I notice that the list of keyboard identifiers in
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#keyset
now has multiple identifiers for certain keys. For example, there are
three identifiers for the comma key: ,, Comma and U+002C.
What is the purpose of having multiple
Hi Cameron,
Cameron McCormack wrote:
Hi Doug.
Doug Schepers:
Further, when a QWERTY keyboard is remapped to a Dvorak layout, but the
labels on the keys remain unchanged, a typist would expect that hitting
the key labeled Q would result in an apostrophe... they would expect
the same
Hi Andrew.
Andrew Cunningham:
I guess I'm not following this.
So you're just looking at the scan codes then of the keys being pressed?
if i press the q/Q key are you looking at a particular physical key key
on the keyboard? i.e. ultimately at the scan codes or virtual key codes?
or are
Cameron McCormack wrote:
So are you using a positional approach using the virtual keys or scan
codes of the physical keyboard, or are you interpreting the keystroke at
a higher level so that key interpretation is mnemonic, i.e. does it
matter which key is typed? or is it the q-key
Andrew Cunningham:
It sounds confused to me, as far as i can tell you're trying to use
positional keyboard concepts in a mnemonic way.
It’s quite possible I’m confused. :)
A q|Q on a QWERTY keyboard will have different scan codes and virtual
key codes that the q|Q key on an AZERTY
Cameron McCormack wrote:
Andrew Cunningham:
so if you want a q|Q key on a US keyboard or a French keyboard to do the
same thing on a web app, you're talking about a higher level
interpretation of what a keyboard is doing. I.e. you're looking at
output rather than at physical keys.
I just now moved the /2006/webapi/Binding4DOM directory on the
dev.w3.org CVS server to /2006/webapi/WebIDL.
http://dev.w3.org/cvsweb/2006/webapi/WebIDL/
So you might get some warnings or other unexpected cvs client
behavior if/when you got update your /2006/webapi working
directory. To
10 matches
Mail list logo
