Open Bug 1354203 (selenium-atoms) Opened 7 years ago Updated 5 months ago

[meta] Remove Selenium atoms from Marionette

Categories

(Remote Protocol :: Marionette, enhancement)

Version 3
enhancement

Tracking

(Not tracked)

People

(Reporter: ato, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: meta)

A long-term goal of Marionette is to remove the dependency on Selenium atoms.  This bug tracks the work needed to remove testing/marionette/atom.js from m-c.

There are a few things that block us from removing the JS fragment atoms in their entirety, most notably that the WebDriver WG has decided to depend on the Selenium getText atom for the foreseeable future due to a lack of cross-browser web platform APIs.
Priority: -- → P3
Alias: selenium-atoms
Depends on: 1354211
Blocks: webdriver
Andreas, in the meeting last week you mentioned that we cannot remove all the Selenium atoms. Which of those remaining would that be? Currently we have getElementText, isElementEnabled, and isElementDisplayed. I would like to file the remaining bugs for removal. Thanks.
Flags: needinfo?(ato)
isElementDisplayed can't be removed as it is in the spec and getElementText may prove tricky as we are waiting on `innerText` moving to be interoperable in browsers.
Flags: needinfo?(ato)
The dependency tree here is correct.  After I patched Element
Clear last week, the only remaining command we need to fix is Is
Element Enabled which shouldn’t be very hard.  That is tracked in
https://bugzil.la/1354201.
Ok, thank you both!
Priority: P3 → P1
Priority: P1 → --
Summary: Remove Selenium atoms from Marionette → [meta] Remove Selenium atoms from Marionette
Severity: normal → S3
Product: Testing → Remote Protocol
No longer depends on: 1354201
You need to log in before you can comment on or make changes to this bug.