From b0b2e0da8a0de59f55117302e01ae2a5f422fbea Mon Sep 17 00:00:00 2001 From: soulgalore Date: Thu, 15 Apr 2021 21:08:24 +0200 Subject: [PATCH] Fix correct chrome.args handling in configuration.json https://github.com/sitespeedio/sitespeed.io/issues/3192 --- lib/cli/cli.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/cli/cli.js b/lib/cli/cli.js index da9c5f3d9..c08da854d 100644 --- a/lib/cli/cli.js +++ b/lib/cli/cli.js @@ -670,7 +670,7 @@ module.exports.parseCommandLine = function parseCommandLine() { .option('browsertime.chrome.args', { alias: 'chrome.args', describe: - 'Extra command line arguments to pass to the Chrome process. Always leave out the starting -- (--no-sandbox will be no-sandbox). ' + + 'Extra command line arguments to pass to the Chrome process. If you use the command line, leave out the starting -- (--no-sandbox will be no-sandbox). If you use a configuration JSON file you should keep the starting --. ' + 'To add multiple arguments to Chrome, repeat --browsertime.chrome.args once per argument. See https://peter.sh/experiments/chromium-command-line-switches/', group: 'Chrome' })