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 27244 - [WebDriver Spec]: Add support for accelKey as meta key to ease the usage of command keys
Summary: [WebDriver Spec]: Add support for accelKey as meta key to ease the usage of c...
Status: RESOLVED WONTFIX
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency treegraph
 
Reported: 2014-11-05 09:53 UTC by Henrik Skupin
Modified: 2016-09-19 16:24 UTC (History)
3 users (show)

See Also:


Attachments

Description Henrik Skupin 2014-11-05 09:53:17 UTC
There are differences in how commands like shortcuts are triggered in chrome scope across platforms. While on Windows and Linux the Ctrl key is used, on OS X it is the Cmd key. That implies that for each shortcut you have to check the platform first, and then set the correct modifier key.

Example:  Open the find bar in Firefox (Linux/Windows: Ctrl+F, OS X: Cmd+F)

To make it easier to use, it would be really helpful if a new "meta" key could be added to the spec. For several test frameworks here at Mozilla we have it named accelKey:

http://mxr.mozilla.org/mozilla-central/source/testing/marionette/EventUtils.js#134

Inside the framework a check for the platform ensures that the correct modifier is used. So it is not a requirement for the test itself.
Comment 1 Brian Burg 2016-09-19 16:21:13 UTC
'Meta' is a different key. https://en.wikipedia.org/wiki/Meta_key

'CommandOrControl' is maybe a better name. But I don't think we should fix this at all. Using browser features with key shortcuts is not specified and in some UAs it won't do anything at all.