commit | d4391fedfec67d69f00396873a11f501a97ee3f1 | [log] [tgz] |
---|---|---|
author | Makoto Shimazu <shimazu@chromium.org> | Mon Mar 09 05:35:16 2020 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Mar 09 05:55:44 2020 |
tree | eced13b2af996d08e9634cf3f87bc4bdb2836c50 | |
parent | b10ddff4a774ac4400a3d9b6f283caf5e5cf7af6 [diff] |
COEP takes effect on a new service worker except for importScripts Currently Cross-Origin-Embedder-Policy header is parsed in ServiceWorkerNewScriptLoader when launching a new service worker. However, the COEP in the response header for the main script isn't applied for the network loader created on launching a service worker because the network loader is created before starting to load the main script. This CL is to pause the service worker's script evaluation until the main script is loaded. Once the main script loaded, new subresource loaders are created by using the COEP value, and they are sent to the service worker. Imported scripts also need to refer to the new value, but the loaders are in different place (ServiceWorkerScriptLoaderFactory), so it'll be addressed in a later patch. Bug: 1039613 Change-Id: Ice82eef86beec2f2f5c5e91f3aa136229f14c3ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2029403 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Auto-Submit: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#748112}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
In the vast majority of cases the only upstream branch that you should need to care about is master
. If you see other branches in the repository, you can generally safely ignore them.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!