[Bug 25968] Needs clearer definition of virtual keyboard's KeyboardEvent.code value if it doesn't emulate physical key event completely

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

--- Comment #1 from Masayuki Nakano <masayuki@d-toybox.com> ---
My most important suggestion is, browsers SHOULD NOT try to guess code values
of printable keys in standard position when a VKB doesn't emulate native
physical keyboard event (i.e., no scancode) and the platform doesn't have API
to compute scancode from virtual keycode.

If browsers did guess in such case, .code value would be untrusted attribute in
such situation but web developers couldn't know whether they were in such case.

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

Received on Wednesday, 4 June 2014 00:54:13 UTC