[Bug 18867] Web developers cannot know whether a key event will cause text input actually

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18867

Egor Khalimonenko <termi1uc1@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |termi1uc1@gmail.com

--- Comment #2 from Egor Khalimonenko <termi1uc1@gmail.com> ---
I am posted the similar proposal to w3 mailing list
http://lists.w3.org/Archives/Public/www-dom/2012JulSep/0108.html

In short, I proposed to "key" and "char" logical division. "char" property is
an input character and it work as it describe in current draft. In the other
hand, "key" property for any character keys with any special keys (Shift, Alt,
Win/OS, Ctrl) is a US-en keyboard layout lowercased character representation
similar to String.fromCharCode(key.keyCode).toLowerCase(). For non-character
keys (http://www.w3.org/TR/DOM-Level-3-Events/#key-values-list) "key" property
stay the same as in current drafg.

In example:
'ы':                     { key: 's', char: 'ы' }
'ы' with Shift:          { key: 's', char: 'Ы', shiftKey : true }
'ы' with Ctrl:           { key: 's', char: '' , ctrlKey : true }
'ы' with Ctrl and Shift: { key: 's', char: '' , shiftKey : true, ctrlKey : true
}

As you can see the "char" property is useful only when it was a character input
in some text field, in other cases we need cross-location case insensitive
value to detect the current keyboard key pressed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.