chore: address selenium-4 branch in readme#566
Merged
KazuCocoa merged 1 commit intoappium:masterfrom Dec 19, 2020
Merged
Conversation
mykola-mokhnach
approved these changes
Dec 19, 2020
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've created a selenium-4 based branch to inherits selenium 4.0.0.a7 (for now) instead of current v3.
It allows us to relax SSL verification so that it can connect to self-certificated SSL server.
I'd like to push the branch as pre-release like
2.0.0.a0to pipy like selenium 4.0.0.a7.For now, Python 3 and selenium v3 cannot connect to the environment because of an exception.
Our main working branch is still v1 (current master) though.
Btw, Python binding v4 still has JSONWP as well, while selenium 4 is basically going to support only W3C