Closed
Bug 1354203
(selenium-atoms)
Opened 8 years ago
Closed 6 months ago
[meta] Remove Selenium atoms from Marionette
Categories
(Remote Protocol :: Marionette, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ato, Unassigned)
References
(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.
Reporter | ||
Updated•8 years ago
|
Priority: -- → P3
Reporter | ||
Updated•8 years ago
|
Alias: selenium-atoms
Reporter | ||
Updated•8 years ago
|
Comment 2•7 years ago
|
||
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)
Comment 3•7 years ago
|
||
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)
Reporter | ||
Comment 4•7 years ago
|
||
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.
Comment 5•7 years ago
|
||
Ok, thank you both!
Reporter | ||
Updated•7 years ago
|
Priority: P3 → P1
Reporter | ||
Updated•6 years ago
|
Priority: P1 → --
Summary: Remove Selenium atoms from Marionette → [meta] Remove Selenium atoms from Marionette
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Product: Testing → Remote Protocol
Comment 6•7 months ago
|
||
(In reply to David Burns :automatedtester from comment #3)
isElementDisplayed can't be removed as it is in the spec and getElementText
may prove tricky as we are waiting oninnerText
moving to be interoperable
in browsers.
Based on this feedback from David it looks like that we are done with removing the usage of possible Selenium Atom usage. Only these two atoms remain in our tree and in the WebDriver classic specification, and it looks like that we aren't able to get them removed.
Lets discuss today and close if that is correct.
Whiteboard: [webdriver:triage]
Comment 7•6 months ago
|
||
We are not going to remove the other atoms. So this work is done.
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Updated•6 months ago
|
Whiteboard: [webdriver:triage]
You need to log in
before you can comment on or make changes to this bug.
Description
•