- From: <bugzilla@jessica.w3.org>
- Date: Wed, 04 Jun 2014 10:44:05 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24739
Masayuki Nakano <masayuki@d-toybox.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #5 from Masayuki Nakano <masayuki@d-toybox.com> ---
(In reply to Gary Kacmarcik from comment #4)
> For the code values, we identify the keys by position for the "writing
> system keys" and by function for the other keys. Since the Sun 'Menu' key
> serves the same purpose as the 'ContextMenu' key, it should be encoded as
> 'ContextMenu'.
Hmm, I don't like your idea "by function for the other keys" because such
definition makes browsers need to compute code value with virtual keycode (or
keysym) and it may depend on modifier state.
However, I believe that you meant "by original function expected by keyboard
vendor for the other key". Then, I can agree with your idea.
> Also, having a generic 'Menu' key would be confusing since it might be
> misinterpreted as the standard key labeled "Menu". If we need to add another
> one, then we'd need to have a prefix that distinguishes it from the other
> "menu" keys.
Wait, you took a mistake. "Menu" key of USB HID is labeled "Props". So, as you
said, it should be "ContextMenu" value for .code, "Props" value should be
removed from the table.
-> REOPEN for the latter issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 4 June 2014 10:44:07 UTC