[Bug 27990] [D3E-key][D3E-code] "#" and "*" button of feature phones should be defined

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

--- Comment #5 from Masayuki Nakano <masayuki@d-toybox.com> ---
I guess that whether they causes inputting "#" or "*" depends on the design of
the device. Some vendor may map them as printable keys, the others may map them
as non-printable keys. For the latter case, these keys should have independent
key names, I think.

Similarly, their .code values are difficult issue. They may be shared with
normal PC's scancode. Even in this case, browser vendors need the guideline of
the key. If using Digit3 and Digit8 for them because of en-US keyboard layout,
they may be conflict with "3" and "8" keys on the phone.

So, for .code value, The spec should define both (1) recommended .code value if
they are mapped to scancode shared with some keys on PC keyboard and (2)
independent .code value if they are not mapped to scancode which is not used on
PC keyboard.

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

Received on Wednesday, 11 February 2015 00:55:09 UTC