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 21966 - D3E spec should prohibit browser vendors name original key name
Summary: D3E spec should prohibit browser vendors name original key name
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL: http://dev.w3.org/2006/webapi/DOM-Lev...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-08 12:40 UTC by Masayuki Nakano
Modified: 2013-07-09 22:31 UTC (History)
4 users (show)

See Also:

Attachments

Description Masayuki Nakano 2013-05-08 12:40:56 UTC 
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.
Comment 1 Masayuki Nakano 2013-05-09 03:55:43 UTC 
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
Comment 2 Gary Kacmarcik 2013-07-09 22:31:10 UTC 
Fixed in ED by removing the section that requires browser vendors to make up their own 'key' values.