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 27130 - [D3E-key]:
Summary: [D3E-key]:
Status: RESOLVED WORKSFORME
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:44 UTC by Habib Virji
Modified: 2015-02-25 01:04 UTC (History)
3 users (show)

See Also:

Attachments

Description Habib Virji 2014-10-22 15:44:36 UTC 
"LaunchMyComputer"
In DOM3 Code, this is still LaunchApp1. Will be nice to have both having same code/key value for the same key.
Comment 1 Masayuki Nakano 2014-10-28 01:26:07 UTC 
It's just a usual example that LaunchApp1 is mapped to LauchMyComputer key.

See GTK and Qt mapping plan of Gecko:
https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent.key

They have both LaunchApp1 key and LaunchMyComputer keys separately. If platform fires a native key event which explicitly specifies application name which will/should be launched, browsers should use the specific names. Otherwise, i.e., platform fires a native key event which is not clear that which application will be launched, browsers should use LaunchApp[0-9]+.
Comment 2 Travis Leithead [MSFT] 2015-02-25 01:04:40 UTC 
Agree with Masayuki's comments.