Bug 1292178 (webdriver-actions)

[meta] Implement actions API that conform to WebDriver in Marionette

NEW
Unassigned

Status

3 years ago
a month ago

People

(Reporter: jgraham, Unassigned)

Tracking

(Depends on: 12 bugs, Blocks: 1 bug, {meta})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
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)
Comment hidden (offtopic)
Comment hidden (offtopic)
Comment hidden (offtopic)
Duplicate of this bug: 1267292
Comment hidden (me-too)
Comment hidden (me-too)
Comment hidden (me-too)
(Reporter)

Comment 10

2 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.
Since #1320389 has been fixed, what else are we missing to get it done?
Summary: [meta] Implement W3C WebDriver-compatible Actions API implementation in marionette. → [TRACKING] Implement actions API that conform to WebDriver in Marionette
(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.
Alias: webdriver-actions
(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.
Duplicate of this bug: 1328914
Depends on: 1332279

Comment 15

2 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.
Priority: -- → P3
All deps are closed, is there anything else missing from this or can we close it?
Flags: needinfo?(mjzffr)
Flags: needinfo?(ato)
Depends on: 1421323
Depends on: 1430851
Depends on: 1431116
Depends on: 1398098
Depends on: 1417955
Depends on: 1422583
Depends on: 1329833
Depends on: 1347234
Added some new dependencies from existing bugs.
Flags: needinfo?(ato)
Depends on: 1255260
Depends on: 1419394
Flags: needinfo?(mjzffr)
Priority: P3 → P1
Summary: [TRACKING] Implement actions API that conform to WebDriver in Marionette → [meta] Implement actions API that conform to WebDriver in Marionette
Depends on: 1405370
Depends on: 1388812
Priority: P1 → --
Depends on: 1443482
Depends on: 1456642
No longer depends on: 1255260
Depends on: 1484157
Depends on: 1490268
No longer depends on: 1456642
Depends on: 1491751
Depends on: 1498901
Keywords: meta
Depends on: 1515879
You need to log in before you can comment on or make changes to this bug.