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 25229 - Shouldn't NumpadComma be NumpadSeparator?
Summary: Shouldn't NumpadComma be NumpadSeparator?
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-02 09:43 UTC by Masayuki Nakano
Modified: 2014-04-08 01:08 UTC (History)
3 users (show)

See Also:

Attachments

Description Masayuki Nakano 2014-04-02 09:43:45 UTC 
The code value of NumpadDecimal is good for i18n. However, the comma key on Numpad's code value is defined as NumpadComma. I think that NumpadSeparator is better for some countries' people.
Comment 1 Gary Kacmarcik 2014-04-07 18:51:57 UTC 
This is another one of those keys that cannot have a name that matches every locale. This key is rare and for the few cases where it is present, we need to have a name that properly identifies it.

Hence the names "Decimal" and "Comma", which are meant to go hand-in-hand to make the keys easy to identify for locales that swap the 2 meanings.

In addition, the name "Separator" is very generic and might lead to confusion.

FWIW, the USB spec, when faced with the same problem, chose "Keypad Comma" as the name for this key. See footnote 27 for Table 12 in the USB HID Usage Tables.
Comment 2 Masayuki Nakano 2014-04-08 01:08:25 UTC 
Indeed, the key is defined as "Comma" in USB spec. My concern is, one of the rare keyboard having this key is Brazilian keyboard (ABNT keyboard), but it's the most popular keyboard layout having the key. Unfortunately, Brazilian people use "." for thousand separator...