blob: a3ccd95768fdbc160af99bc647f1023a3dbc5ddc (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
# Chrome and Chromium
When running Chrome, there are some useful command line arguments.
You can inform `wpt` of the release channel of Chrome using `--channel`.
`wpt` is able to find the correct binary in the following cases:
* On Linux for stable, beta and dev channels if
`google-chrome-{stable,beta,unstable}` are in `PATH`;
* On Mac for stable and canary channels if the official DMGs are installed.
In other cases, you will need to specify the path to the Chrome binary with
`--binary`. For example:
```bash
./wpt run --channel dev --binary /path/to/non-default/google-chrome chrome
```
Note: when the channel is "dev", `wpt` will *automatically* enable all
[experimental web platform features][1]
(chrome://flags/#enable-experimental-web-platform-features) by passing
`--enable-experimental-web-platform-features` to Chrome.
If you want to enable a specific [runtime enabled feature][1], use
`--binary-arg` to specify the flag(s) that you want to pass to Chrome:
```bash
./wpt run --binary-arg=--enable-blink-features=AsyncClipboard chrome clipboard-apis/
```
To use a custom chromedriver build, build the `chromedriver` target in your chromium checkout,
and then pass `--webdriver-binary /path/to/non-default/chromedriver` to `wpt run`.
[A detailed explanation is available](chrome-chromium-installation-detection.html)
for more information on how wpt detects and installs the components for Chrome and Chromium.
[1]: https://chromium.googlesource.com/chromium/src/+/main/third_party/blink/renderer/platform/RuntimeEnabledFeatures.md
|
