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.
It appears that we follow the spec here and Selenium is out of date. Code is at http://mxr.mozilla.org/mozilla-central/source/testing/marionette/marionette-server.js#1363  https://dvcs.w3.org/hg/webdriver/raw-file/tip/webdriver-spec.html#timeouts-1
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
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.