Fix issue with proxy server auth in chrome headless mode #234
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
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.
Fix issue with proxy server auth in chrome headless mode.
When using a proxy server that has authentication with Chrome in headless mode, SeleniumBase will now use PyVirtualDisplay (already implemented in https://github.com/seleniumbase/SeleniumBase/blob/master/seleniumbase/fixtures/base_case.py) rather than using Chrome's built-in headless mode because Chrome doesn't allow extensions when using headless mode. This assumes that the user's system already supports Xvfb (the headless display system) in order to run with PyVirtualDisplay.
See https://bugs.chromium.org/p/chromium/issues/detail?id=706008 , where a member from the Chromium team says: "Headless mode doesn't currently support extensions".