941152 - setSearchTimeout not matching webdriver command implicitlyWait

Status: RESOLVED INVALID

(Remote Protocol :: Marionette, defect)

Description

[Andreas Tolfsen ❲:ato❳]

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

[David Burns :automatedtester]

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

Comment 2

[Andreas Tolfsen ❲:ato❳]

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.