WebDriver:PerformActions: keydown for " " behaves differently from keyDown for u"\ue00d"
Categories
(Remote Protocol :: Marionette, enhancement, P2)
Tracking
(firefox76 fixed)
| Tracking | Status | |
|---|---|---|
| firefox76 | --- | fixed |
People
(Reporter: impossibus, Assigned: jgraham)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
47 bytes,
text/x-phabricator-request
|
Details |
Comment 1•8 years ago
|
||
Comment 2•8 years ago
|
||
| Reporter | ||
Comment 3•8 years ago
|
||
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
| Assignee | ||
Comment 5•6 years ago
|
||
Is there more to this than
diff --git a/testing/marionette/event.js b/testing/marionette/event.js
index 2143094dc493..77568b424e39 100644
--- a/testing/marionette/event.js
+++ b/testing/marionette/event.js
@@ -890,6 +890,7 @@ const VIRTUAL_KEYCODE_LOOKUP = {
"\uE00A": "VK_ALT",
"\uE00B": "VK_PAUSE",
"\uE00C": "VK_ESCAPE",
+ " ": "VK_SPACE", // printable
"\uE00D": "VK_SPACE", // printable
"\uE00E": "VK_PAGE_UP",
"\uE00F": "VK_PAGE_DOWN",
| Assignee | ||
Comment 7•6 years ago
|
||
Updated•6 years ago
|
Comment 8•6 years ago
|
||
The spec seems a bit confusing to me: https://w3c.github.io/webdriver/#keyboard-actions
IIUC, the first table says "Space" is coded to \uE00D, but the second table says "Space"->" " while "Shift+Space"->\uE00D. Am I just reading this wrong?
| Assignee | ||
Comment 9•6 years ago
|
||
What that means in the spec is that using SendKeys("\uE00D") should imply the shift modifier. I suspect that's a bug in which the second column of the second table was used for two different things that are usually equivalent, but not here, but I'm not sure. Want to file a spec issue?
In any case that doesn't affect actions which don't do implied shift.
Comment 10•6 years ago
|
||
Comment 13•6 years ago
|
||
What that means in the spec is that using SendKeys("\uE00D") should imply the shift modifier
I see. I think I understand now. For some reason, the Space key has its shifted character defined as \uE00D in the second table, but the this Alternate Key does not have a different Normalized Key Value (unlike those numpad keys, for example) -- in other words, both Space and Shift+Space normalize to " ". If so, then I think the spec is coherent. It was a bit confusing to me as someone who's not familiar with the spec language (like, I should've probably started from the algorithms instead of these tables and definitions).
the second column of the second table was used for two different things that are usually equivalent, but not here
I'm not sure what you meant here.
Comment 14•6 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Description
•