Description
The Agent CLI Configuration documentation lists --ignore-https-errors as an available option for the open command:
playwright-cli open --ignore-https-errors # ignore HTTPS errors
However, this flag is not recognized by the currently released version 0.1.13 of @playwright/cli.
Reproduction Steps
-
Install the latest version globally:
npm install -g @playwright/cli@latest
-
Check the version:
playwright-cli --version
# Output: 0.1.13
-
Run open --help and observe available flags:
playwright-cli open --help
Output:
Options:
--browser browser or chrome channel to use, possible values: chrome, firefox, webkit, msedge.
--config path to the configuration file, defaults to .playwright/cli.config.json
--headed run browser in headed mode
--persistent use persistent browser profile
--profile path to a persistent user data directory.
-
Attempt to use the flag:
playwright-cli open --ignore-https-errors https://example.com
Output:
Error: unknown option: ignore-https-errors
Expected Behavior
The --ignore-https-errors flag should be accepted by the CLI and passed to the underlying Playwright browser context, as documented.
Actual Behavior
The flag is rejected as unknown.
Investigation
Looking at the released npm package (@playwright/cli@0.1.13), the help.json defines the following flags for the open command:
"flags": {
"browser": "string",
"config": "string",
"headed": "boolean",
"persistent": "boolean",
"profile": "string"
}
The ignore-https-errors flag is absent. The same documentation page also lists --device, --viewport-size, --proxy-server, --proxy-bypass, and --user-agent as open flags; all of these are similarly unrecognized by the CLI.
Workaround
Users can configure ignoreHTTPSErrors via the JSON config file (.playwright/cli.config.json):
{
"browser": {
"contextOptions": {
"ignoreHTTPSErrors": true
}
}
}
However, this is less convenient than a direct CLI flag, especially for ad-hoc commands or CI environments.
Environment
@playwright/cli: 0.1.13
playwright-core: 1.61.0-alpha-1778188671000
- Node.js: 20+
- OS: Linux / macOS / Windows (all affected)
Description
The Agent CLI Configuration documentation lists
--ignore-https-errorsas an available option for theopencommand:playwright-cli open --ignore-https-errors # ignore HTTPS errorsHowever, this flag is not recognized by the currently released version
0.1.13of@playwright/cli.Reproduction Steps
Install the latest version globally:
Check the version:
playwright-cli --version # Output: 0.1.13Run
open --helpand observe available flags:Output:
Attempt to use the flag:
Output:
Expected Behavior
The
--ignore-https-errorsflag should be accepted by the CLI and passed to the underlying Playwright browser context, as documented.Actual Behavior
The flag is rejected as unknown.
Investigation
Looking at the released npm package (
@playwright/cli@0.1.13), thehelp.jsondefines the followingflagsfor theopencommand:The
ignore-https-errorsflag is absent. The same documentation page also lists--device,--viewport-size,--proxy-server,--proxy-bypass, and--user-agentasopenflags; all of these are similarly unrecognized by the CLI.Workaround
Users can configure
ignoreHTTPSErrorsvia the JSON config file (.playwright/cli.config.json):{ "browser": { "contextOptions": { "ignoreHTTPSErrors": true } } }However, this is less convenient than a direct CLI flag, especially for ad-hoc commands or CI environments.
Environment
@playwright/cli: 0.1.13playwright-core: 1.61.0-alpha-1778188671000