Let v4 support w3c drivers

[shinxi]

• Add w3c capabilities to the session command to let w3c drivers work correctly.

Reference: webdriverio/webdriverio#4380

Proposed changes

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have proposed the same patch to the new v5 repository

Further comments

Reviewers: @christian-bromann

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

[emilyrohrbough]

How has this been tested? One which browsers has this been tested in?

[emilyrohrbough]

These don't match what exists in webdriver v5:
https://github.com/webdriverio/webdriverio/blob/e79328564e049fe6c81f0319ffe89d9293462e69/packages/webdriverio/src/constants.js#L369

looking at goog:chromeOptions and moz:firefoxOptions

[shinxi]

@emilyrohrbough goog:chromeOptions and moz:firefoxOptions are valid w3c browser specific options.
See https://www.w3.org/TR/webdriver1/#dfn-extension-capability, https://developer.mozilla.org/en-US/docs/Web/WebDriver/Capabilities.

[shinxi]

How has this been tested? One which browsers has this been tested in?

@emilyrohrbough Sure, I'll add some tests later.

[christian-bromann]

@shinxi I highly recommend to switch to v5 because v4 (even with this patch) is not 100% compatible with the WebDriver spec. You will end up spending more time fixing those kind of issues than rewriting your test suite into v5.