This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23748 - Shouldn't getModifierState() definition refer Modifiers Keys which are defined in .key value?
Summary: Shouldn't getModifierState() definition refer Modifiers Keys which are define...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on: 23750
Blocks:
  Show dependency tree / graph
 
Reported: 2013-11-07 02:45 UTC by Masayuki Nakano
Modified: 2014-04-07 23:38 UTC (History)
4 users (show)

See Also:

Attachments

Description Masayuki Nakano 2013-11-07 02:45:21 UTC 
https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#widl-KeyboardEvent-getModifierState

Currently key names are defined by each group. Modifier key is defined in https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#h4_keys-modifier

So, shouldn't the getModifierState() definition refer the modifier key name table for its argument?

I.e., on Linux, it's better to use "Super" or "Hyper" when Widnows Logo key is pressed.
Comment 1 Gary Kacmarcik 2014-04-07 23:38:58 UTC 
Fixed in ED