[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

Masayuki Nakano <masayuki@d-toybox.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugs@pettay.fi

--- Comment #2 from Masayuki Nakano <masayuki@d-toybox.com> ---
And Olli thinks that it's odd to guess non-printable .code value when browsers
are not sure the printable keys' code values.
https://bugzilla.mozilla.org/show_bug.cgi?id=1017383#c2

I think that it's okay browsers to set proper code value when a native virtual
keycode includes position information e.g., SHIFT_LEFT, SHIFT_RIGHT, or is only
generated with a scan value like SPACE.

However, indeed, if browsers shouldn't *guess* code value always, it makes the
spec and behavior simpler.

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

Received on Wednesday, 4 June 2014 01:24:58 UTC