setSearchTimeout not matching webdriver command implicitlyWait

RESOLVED INVALID

Status

Testing
Marionette
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: ato, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

4 years ago
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.
(Reporter)

Comment 2

4 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
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.