Skip to content

Add Chrome CLI flag options to Chrome Driver Config - #41

Merged
undera merged 2 commits into
undera:masterfrom
darrinh:chrome-cli-flags
Nov 4, 2026
Merged

undera merged 2 commits into
undera:masterfrom
darrinh:chrome-cli-flags

Conversation

@darrinh

@darrinh darrinh commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Adds six optional Chrome command-line flags to the Chrome Driver Config element and GUI, each with its own unit test:

  • --disable-gpu
  • --disable-dev-shm-usage
  • --disable-extensions
  • --disable-background-networking
  • --metrics-recording-off
  • --mute-audio

These are commonly required for headless/containerized load-testing environments where Chrome's default resource usage is problematic. Previously the only workaround was wrapping the chromedriver/chrome binaries in a custom script; the flags now live in the plugin itself, alongside the existing No-sandbox option.

All 273 project tests pass.

🤖 Generated with Claude Code

darrinhodges and others added 2 commits November 4, 2026 15:04
Adds six optional Chrome command-line flags to the Chrome Driver
Config element and GUI, with unit tests:
  --disable-gpu, --disable-dev-shm-usage, --disable-extensions,
  --disable-background-networking, --metrics-recording-off,
  --mute-audio

Useful for headless/containerized load-testing environments where
Chrome's default resource usage is problematic.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
@undera
undera merged commit 94c642b into undera:master Nov 4, 2026
1 check passed
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.

3 participants