Closed
Bug 941152
Opened 11 years ago
Closed 11 years ago
setSearchTimeout not matching webdriver command implicitlyWait
Categories
(Remote Protocol :: Marionette, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ato, Unassigned)
References
(Blocks 1 open bug, )
Details
Marionette uses "setSearchTimeout" for defining the timeout value when
implicitly waiting for elements to appear in the DOM while the
expected webdriver command is "implicitlyWait".
This incompatibility makes it harder to use Marionette directly
without maintaining a WebDriver-to-Marionette command conversion set.
Comment 1•11 years ago
|
||
It appears that we follow the spec[1] here and Selenium is out of date.
Code is at http://mxr.mozilla.org/mozilla-central/source/testing/marionette/marionette-server.js#1363
[1] https://dvcs.w3.org/hg/webdriver/raw-file/tip/webdriver-spec.html#timeouts-1
Reporter | ||
Comment 2•11 years ago
|
||
OK. This is off-topic but how will we handle the migration to keep
compatibility with the Selenium project and its myriad of client
bindings?
The same questions applies to getWindows, getCurrentWindows,
getWindowHandles, getCurrentWindowHandle, and getWindowHandle.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•