Selenium-Remote-Driver

Should prevent a bad reach-out to saucelabs from making installs go TU

see changes

We fixed a couple of bugs, and made Edge compatible with the new Chrome based MicrosoftEdge.

see Changes

see CHANGES as per usual

bad logic as always, kings

Chromedriver team decided to finally implement WC3 mode, but made sure to throw rather than falling back to JSONWire methods where WC3 falls short, so have fun with your tests failing.

Fix #432
Selenium-Remote-Driver-1.35.tar.gz

Removal of .so files not needed in the Firefox/ dir

Why they chose lunatic default settings is beyond me. Not feeling the quality from that set these days.

Various patches from various sources. Light on testing, unfortunately.

Fixes bug with set_timeouts WC3 standard changing out from under us, and a bug with direct driver sessions not being terminated under certain circumstances.

1.30 09-17-2018 TEODESIAN
[BUG FIXES]
- Fix broken name selector polyfill when using Selenium::Firefox directly
- Fix switch_to_frame(undef) brokenness due to unneeded polyfill
- Correct POD information about how to use raw firefox profiles
- Advertise Microsoft Browser Standalone Drivers (Edge, IE)

Also some bugfixes, see Changes as usual

Selenium-Remote-Driver-1.29.tar.gz

Chromedriver's WC3 compatibility is worse than useless, so we've totally disabled it for now.

Other than that, submit() on firefox should work for elements again.

Forced fallback to JSONWire javascript execution for "WC3 capable" chromedrivers, because it causes bizarre issues.

Also fixed an ID selector shim issue where paths with . would not be selectable.

Fixes a bug with chrome's get/set window size methods by forcing usage of the JSONWire protocol in WD3 mode (some "WD3" chrome/drivers don't have it yet).

A few of the JS polyfills for JSONWire behaviour have been fixed to do nothing in edge cases, and the POD advises on how to avoid said cases in the future.

is_enabled was broken in 1.21, it is now fixed.

Passing extra_capabilities to firefox and chrome was previously broken. This has now been remedied, but in a non-optimal way due to the difficulty in figuring out ahead of time whether a server used supports WC3 webdriver or not. Hopefully in the future we won't need such bogosity.

See the POD's COMPATIBILITY section for more information.

Implements WC3 webdriver spec, while preserving backwards-compatibility. Tries to add shims for drivers that aren't quite there yet (all of them) to keep API from changing.
Selenium-Remote-Driver-1.21.tar.gz