[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 #7 from Masayuki Nakano <masayuki@d-toybox.com> ---
(In reply to Gary Kacmarcik from comment #6)
> For 'key':
> I can see this either generating '#' and '*', or being considered
> unprintable. We should match whatever the current common behavior is.

Yeah, I'm asking the behavior to a vendor. However, I think that D3E key should
define specific names for the keys because some vendors may make them
non-printable keys.

> For 'code':
> NumpadAsterisk and NumpadHash seem like the best choices since these are
> distinct keys.

Agreed.

> 'Digit3' and 'Digit8' are keys that vary based on the locale and just happen
> to map to '3' and '8' on US layouts. They are conpletely different keys on
> different layouts and have no relation to the phone pad '*' and '#' keys. 
> Thus, these values are not appropriate for use here.

I agree with your idea about the locale issue. However, I still think that
there should be some guide lines if some vendor cannot use independent scancode
for them. In such case, web browsers cannot distinguish them as Numpad* if the
platform doesn't have independent virtual keycode.

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

Received on Wednesday, 11 February 2015 02:00:38 UTC