21966 2013-05-08 12:40:56 +0000 D3E spec should prohibit browser vendors name original key name 2013-07-09 22:31:10 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - DOM3 Events unspecified PC Windows NT RESOLVED FIXED http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#keys-Guide P2 normal --- 1 masayuki garykac garykac mike mounir www-dom public-webapps-bugzilla oldest_to_newest 87420 0 masayuki 2013-05-08 12:40:56 +0000 http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#keys-Guide said that: 2.2 If there is no appropriate key value in the key values set, then a key value must be devised. I think that any browser vendors shouldn't name undefined key name by D3E spec because it may cause different implementation between browsers. Browser vendors should file a spec bug for requesting to register new key name to the spec, first. 87478 1 masayuki 2013-05-09 03:55:43 +0000 When you agree with this idea, you need to change the document here: http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#key-values 90547 2 garykac 2013-07-09 22:31:10 +0000 Fixed in ED by removing the section that requires browser vendors to make up their own 'key' values.