Skip to content

feat(browser): support custom Chrome flags via VIBIUM_CHROME_ARGS#178

Open
youdie006 wants to merge 1 commit into
VibiumDev:mainfrom
youdie006:feat/custom-chrome-flags
Open

feat(browser): support custom Chrome flags via VIBIUM_CHROME_ARGS#178
youdie006 wants to merge 1 commit into
VibiumDev:mainfrom
youdie006:feat/custom-chrome-flags

Conversation

@youdie006

Copy link
Copy Markdown

Summary

chromeArgs built a fixed flag list, so there was no way to pass extra Chrome flags (e.g. --no-sandbox) needed to run as root in CI/container environments (#141, option 1 from the issue).

Fix

clicker/internal/browser/launcher.go: read VIBIUM_CHROME_ARGS (space-separated, empty tokens skipped) and append the flags to goog:chromeOptions, with no client-SDK changes — so it works across all language clients. Added launcher tests covering the set / unset / whitespace-padded env cases.

Closes #141

chromeArgs built a fixed flag list, so there was no way to pass extra Chrome
flags (e.g. --no-sandbox) needed to run as root in CI/container environments.
Read VIBIUM_CHROME_ARGS (space-separated, empty tokens skipped) and append the
flags to goog:chromeOptions, with no client-SDK changes.

Closes VibiumDev#141
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.

Support passing custom Chrome flags (e.g. --no-sandbox) for CI/container environments

1 participant