Titus Fortner

Ok, because I want to allow setting: 1. Capabilities 2. SauceOptions 3. DataCenter 4. Enabled/Disalbed It does not make sense to do this all as a bunch of different constructors,...

Updated again: 1. Enabled by default because that's what Registering an Extension should do 2. Disable by one of: * Set Environment Variable of `"SAUCE_DISABLED"` to `"true"` * Set System...

Hmm, not sure why local example isn't passing, since it should be exactly the same as disabled test. They work locally and that error indicates the driver and browser versions...

Let me figure out why it is failing the test first. 😦

@diemol do we need to do this in the other bindings?

my vote is that until we can support it, we should throw an error rather than get the wrong thing

I haven't looked at this code in quite a while, but I suspect it will be similar in approach to what @nvborisenko did here: https://github.com/SeleniumHQ/selenium/pull/13229/files

@diemol Do we need to check Ruby/Python/JS for this as well?

@Purus are you still interested in working on this?

I'm assuming there's no easy way to mark these as deprecated? Do we want to wait for 5.0 to make this change?