Skip to content

use cached browsers when chrome for testing is unavailable - #14

Merged
Mzack9999 merged 2 commits into
mainfrom
legacy-chromium-cache
Nov 13, 2026
Merged

Mzack9999 merged 2 commits into
mainfrom
legacy-chromium-cache

Conversation

@Mzack9999

Copy link
Copy Markdown
Member

When the latest Chrome for Testing version cannot be fetched or downloaded, Browser.Get now uses a cached older Chrome for Testing build or else the newest valid chromium-<revision> directory that go-rod left in the browser cache, so an offline upgrade keeps headless mode working. An explicit NewChromeForTesting version, an explicit Revision and a canceled context still fail as before, and the new tests fail without the change.

Comment thread lib/launcher/browser.go Dismissed
@Mzack9999
Mzack9999 merged commit 220d4b9 into main Nov 13, 2026
7 checks passed
@Mzack9999
Mzack9999 deleted the legacy-chromium-cache branch November 13, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants