Use the new headless Chrome on the pre-registered driver#2726
Merged
twalpole merged 1 commit intoteamcapybara:masterfrom Dec 11, 2023
Merged
Use the new headless Chrome on the pre-registered driver#2726twalpole merged 1 commit intoteamcapybara:masterfrom
twalpole merged 1 commit intoteamcapybara:masterfrom
Conversation
Earlier this year (2023), Chrome released Chrome for Testing, a new Chrome flavor that targets the testing and automation use cases. This flavor is accessible using the `--headless=new` option since Chrome 109, released January 1, 2023. This new mode supports the full browser capabilities, including running extensions. The default headless mode is still pointed to `--headless=old` for now, but it's planned to be changed to `new` over time. This commit explicitly chooses the `new` headless mode, that uses Chrome for Testing.
|
Just curious if there's an ETA on releasing a new version with this fix. |
jagthedrummer
added a commit
to bullet-train-co/bullet_train
that referenced
this pull request
Dec 14, 2023
See this issue on Capybara for additional details: teamcapybara/capybara#2726 This PR just registers a new version of `:selenium_chrome_headless` instead of using the one registered in the `capybara` gem. The new one just mirrors the fix that's already been applied to the gem, but not yet released to rubygems.org. Once a new version of `capybara` is out, we can remove the custom driver.
jagthedrummer
added a commit
to bullet-train-co/bullet_train
that referenced
this pull request
Dec 14, 2023
* Trying to debug a flaky test * will this help * Fix for new versions of Chrome/webdriver See this issue on Capybara for additional details: teamcapybara/capybara#2726 This PR just registers a new version of `:selenium_chrome_headless` instead of using the one registered in the `capybara` gem. The new one just mirrors the fix that's already been applied to the gem, but not yet released to rubygems.org. Once a new version of `capybara` is out, we can remove the custom driver. * dang linter * Don't actually need that
Contributor
Author
|
For folks following this and waiting for a gem update: Selenium released this week a version supporting the old headless mode |
Contributor
|
IMHO it is too early to make this default. New headless mode broke (or make flaky) a lot of Chrome automated usage I have seen (random, not even using Selenium or Capybara). |
Member
|
Then you have the freedom to setup your own config |
5 tasks
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
4 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.
Earlier this year (2023), Chrome released Chrome for Testing, a new Chrome flavor that targets testing and automation use cases. This flavor has been accessible using the
--headless=newoption since Chrome 109, released on January 1, 2023. This new mode supports the full browser capabilities, including running extensions.The default headless mode is still pointed to
--headless=oldfor now, but it's planned to be changed tonewover time.This commit explicitly chooses the
newheadless mode, that uses Chrome for Testing.Solves #2725