Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-08-11 16:35:33 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update web-platform-tests to revision 50ff4f970fd8592a9f436d4e86e7d572de143260

Browse source
This commit is contained in:
WPT Sync Bot 2018-09-20 21:31:18 -04:00
parent 82bbf3ad45
commit 8ea5658199
150 changed files with 4737 additions and 998 deletions
Download patch file Download diff file Expand all files Collapse all files

39
tests/wpt/web-platform-tests/docs/_running-tests/chrome.md
View file

@ -2,40 +2,27 @@
layout: page
title: Chrome
---
When running Chrome, there are some additional useful command line arguments.
When running Chrome, there are some useful command line arguments.
As with most products, you can use a different binary with `--binary`, e.g., to
run Chrome Dev on Linux:
You can inform `wpt` of the release channel of Chrome using `--channel`.
However, `wpt` currently does not support installing Chrome or finding the
Chrome binary of a specific channel, so you would also need to specify the path
to the Chrome binary with `--binary`. For example, to run Chrome Dev on Linux:
```
./wpt run --binary `which google-chrome-unstable` chrome
./wpt run --channel dev --binary `which google-chrome-unstable` chrome
```
Extra arguments to Chrome can be passed with `--binary-args`.
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.
To enable all [experimental web platform features](https://www.chromium.org/blink/runtime-enabled-features) (chrome://flags/#enable-experimental-web-platform-features):
```
./wpt run --binary-arg=--enable-experimental-web-platform-features chrome fullscreen/
```
To enable a specific [runtime enabled feature](http://dev.chromium.org/blink/runtime-enabled-features):
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:
```
./wpt run --binary-arg=--enable-blink-features=AsyncClipboard chrome clipboard-apis/
```
To bypass device selection and use mock media for tests using `getUserMedia`:
```
./wpt run --binary-arg=--use-fake-ui-for-media-stream --binary-arg=--use-fake-device-for-media-stream chrome mediacapture-streams/
```
Note: there's an [open issue for doing this using WebDriver](https://github.com/web-platform-tests/wpt/issues/7424).
Some of the above are most useful in combination, e.g., to run all tests in
Chrome Dev with experimental web platform features enabled:
```
./wpt run --binary `which google-chrome-unstable` --binary-arg=--enable-experimental-web-platform-features chrome
```
[1]: https://www.chromium.org/blink/runtime-enabled-features