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 27131 - [D3E-key]:
Summary: [D3E-key]:
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-22 15:48 UTC by Habib Virji
Modified: 2015-02-25 01:05 UTC (History)
3 users (show)

See Also:

Attachments

Description Habib Virji 2014-10-22 15:48:14 UTC 
"Device Keys" 
- What's the use of these keys? These keys will be handled by respective OS. How are these keys value useful for the browser application?
Comment 1 Masayuki Nakano 2014-10-28 01:18:22 UTC 
They should be mapped to native virtual keycode values which have same meaning. As you said, on some platforms, they are hidden by OS or toolkit. However, they could be fired. Actually, I confirmed that some of them are fired with some condition.

Anyway, these key values are important for Mozilla because we need to represent all possible keys as DOM key events especially on Firefox OS. When web technology is used for implementing (semi-)native applications, it's worthwhile to define all possible DOM key names.