Use new headless mode in Google Chrome #215
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
replaceafill
force-pushed
the
dev/fix-chrome
branch
2 times, most recently
from
6c80060 to
7cf5da2
Compare
replaceafill
force-pushed
the
dev/fix-chrome
branch
from
7cf5da2 to
c755a8f
Compare
This replaces the Chrome for Testing version of Chrome with the standard version. Selenium Manager is still used to download the ChromeDriver version that matches the standard version.
replaceafill
force-pushed
the
dev/fix-chrome
branch
from
c755a8f to
28ace0d
Compare
Dhwaniartefact
approved these changes
Feb 7, 2025
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 uses the new headless mode in Google Chrome. The old mode stopped working in our setup with Chrome 132.
Unfortunately, the Chrome for Testing alternative which is more efficient than the standard version seems problematic to handle sessions switches between the Storage Service and the Dashboard resulting in flaky behavior, so this replaces it with the standard Google Chrome browser.
Connected to archivematica/Issues#1720