Update default chromedriver to 2.31 #290
Merged
Conversation
This file contains 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
UsainBloot
force-pushed
the
chromedriver2.31
branch
from
2bb1e17 to
6ad6331
Compare
|
@vvo, @stephenash, let me know if there are any issues with this PR. |
|
Any progress on this? I would be keen to see it in. |
|
Yeah, would be awesome to be able to remove xvfb! |
|
published |
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.
Chromium released chromedriver 2.31 yesterday
Defaulting chromedriver to 2.31 will fix issues when trying to use the sendKeys API (input keystrokes to the browser) when using Chrome headless.
Details of the fix can be found in this bug tracker
https://bugs.chromium.org/p/chromedriver/issues/detail?id=1772
With merge request here
https://codereview.chromium.org/2952383002
Binaries available here:
https://chromedriver.storage.googleapis.com/index.html?path=2.31/