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 25373 - "NonConvert" (key) vs. "NoConvert" (code)
Summary: "NonConvert" (key) vs. "NoConvert" (code)
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:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-17 09:13 UTC by Masayuki Nakano
Modified: 2014-04-27 17:21 UTC (History)
3 users (show)

See Also:

Attachments

Description Masayuki Nakano 2014-04-17 09:13:10 UTC 
I'm not sure this is intentional difference or a bug.

In code value table, Muhenkan key is defined as "NoConvert".

However, in key value table, it is defined as "NonConvert".

Additionally, some explanation about key value use "Nonconvert".

I.e., "No" vs. "Non". And capitalize the c of "convert" or not.
Comment 1 Gary Kacmarcik 2014-04-23 00:07:21 UTC 
This was not intentional.  They should be the same.

I don't have a strong preference for one over the other, but think that "NonConvert" is reasonable.
Comment 2 Gary Kacmarcik 2014-04-23 00:42:15 UTC 
Changing to "NonConvert" for |key| and |code| values.
Comment 3 Gary Kacmarcik 2014-04-27 17:21:20 UTC 
Fixed in latest ED:
https://dvcs.w3.org/hg/dom3events/rev/21cd9f302b38