Open
Bug 1292178
(webdriver-actions)
Opened 8 years ago
Updated 1 year ago
[meta] Implement actions API that conform to WebDriver in Marionette
Categories
(Remote Protocol :: Marionette, enhancement)
Remote Protocol
Marionette
Tracking
(Not tracked)
NEW
People
(Reporter: jgraham, Unassigned)
References
(Depends on 7 open bugs, Blocks 1 open bug)
Details
(Keywords: meta)
Now the specification for W3C WebDriver actions is taking shape, it's appropriate to start implementing the protocol and semantics of this API in marionette and exposing it via GeckoDriver.
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Depends on: 1303234
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Comment hidden (offtopic) |
Comment hidden (me-too) |
Comment hidden (me-too) |
Comment hidden (me-too) |
Reporter | ||
Comment 10•8 years ago
|
||
This is being actively worked on and we are well aware of its importance. It is also a large and complex part of the specification to get right. Please don't spam the bug with me-too style comments.
Depends on: 1320389
Comment 11•7 years ago
|
||
Since #1320389 has been fixed, what else are we missing to get it done?
Updated•7 years ago
|
Summary: [meta] Implement W3C WebDriver-compatible Actions API implementation in marionette. → [TRACKING] Implement actions API that conform to WebDriver in Marionette
Comment 12•7 years ago
|
||
(In reply to Marek Lewandowski from comment #11) > Since #1320389 has been fixed, what else are we missing to get it done? Yes, there is plenty of work left on this, but it has not all been scoped. In particular, we need to write Web Platform Tests so that we can prove our implementation. We are also missing the implementation of anything to do with pointers. It’s also prudent to point out that Selenium needs to write a shim so that it can speak to W3C WebDriver-conforming drivers, since the new action API is substantially different.
Updated•7 years ago
|
Alias: webdriver-actions
Comment 13•7 years ago
|
||
(In reply to Andreas Tolfsen ‹:ato› from comment #12) Thank you Andreas for your insights. > It’s also prudent to point out that Selenium needs to write a shim so that > it can speak to W3C WebDriver-conforming drivers, since the new action API > is substantially different. Can I ask you to provide a link to Selenium issue for this? So that we can keep an eye on it.
Depends on: 1328726
Depends on: 1337133
Depends on: 1341415
Depends on: 1345653
Depends on: 1357590
Comment 15•7 years ago
|
||
What is the current status on this? I recently used the GeckoDriver 0.16.1 via Selenium 3.4 and found an action sequence to not have the expected result, namely: KeyDown(Ctrl) Click(option1) Click(option2) KeyUp(Ctrl) This was executed on a select element with "multiple" attribute and the Ctrl-down did not appear to work correctly, with only the second option being selected at the end. Should i file a new bug for this?
(In reply to Harald Brunner from comment #15) > > This was executed on a select element with "multiple" attribute and the > Ctrl-down did not appear to work correctly, with only the second option > being selected at the end. Should i file a new bug for this? This sounds like https://github.com/mozilla/geckodriver/issues/645 -- I still need to look into it. Should be able to do so relatively soon.
Depends on: 1367430
Depends on: 1370403
Depends on: 1385476
Updated•7 years ago
|
Priority: -- → P3
Comment 17•6 years ago
|
||
All deps are closed, is there anything else missing from this or can we close it?
Flags: needinfo?(mjzffr)
Flags: needinfo?(ato)
Flags: needinfo?(mjzffr)
Updated•6 years ago
|
Priority: P3 → P1
Summary: [TRACKING] Implement actions API that conform to WebDriver in Marionette → [meta] Implement actions API that conform to WebDriver in Marionette
Updated•6 years ago
|
Priority: P1 → --
Updated•5 years ago
|
Type: defect → enhancement
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•