Convert Capabilities to W3C compatible #678
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OndraM
force-pushed
the
w3c-capabilitites
branch
from
cdef7d4 to
a6cad80
Compare
OndraM
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #676 and is part of #469.
The aim is to convert non-W3C compliant capabilities to their W3C counterparts.
No change in current code is needed - you still set the "old" capabilities and the new ones get converted automatically before browser session creation. However if you already set the new ones, you are ok as well (if you use only W3C-compatible remote browsers).
In php-webdrver 2.0 (#657) the
DesiredCapabilitieswill get revamped so that it only support W3C capabilities (and no conversion will be needed).