Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Handle leadfoot-specific capabilities in desiredCapabilities #137

Closed
jason0x43 opened this issue Feb 7, 2018 · 0 comments
Closed

Handle leadfoot-specific capabilities in desiredCapabilities #137

jason0x43 opened this issue Feb 7, 2018 · 0 comments

Comments

@jason0x43
Copy link
Member

In Leadfoot 2.0.x, leadfoot-specific values in the desiredCapabilities object, such as brokenMouseEvents, are sent to Selenium but not maintained afterwords, at least not by all versions of Selenium or WebDrivers. This means that if a user specifies brokenMouseEvents: true as a capability, it will likely be ignored. Ideally, if a user passes in such a capability, leadfoot should add it to the final capabilities list.

Possibly this should be done through a leadfoot object in the capabilities list so that leadfoot can separate capabilities requested of leadfoot from those requested of the webdriver/selenium.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant