commit | b5c4ae1193387f99dc2bd7e723ed8561e56a137f | [log] [tgz] |
---|---|---|
author | Ian Clelland <iclelland@chromium.org> | Mon Aug 23 20:18:27 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Aug 23 20:41:56 2021 |
tree | 1536c07dd70571ca4a95e67fa698dd9cb74882bc | |
parent | a966f07e9b11fa66e92fdee3fe78c9a19605c6ad [diff] |
Reporting: Allow document token to change Since the RenderFrameHostImpl is reused for same-origin navigations, the reporting source token must be able to change when a new document is loaded into the frame. This is important for reporting isolation when reports are still queued for the old document. WPT is added to catch the situation where not changing this token would cause previously queued reports to be sent to the new document's configured endpoints. This is part of a series of CLs implementing V1 reporting isolation. A summary of the architectural changes introduced can be found at https://docs.google.com/document/d/1RmEz17pGSUQITPoRKV4s3IBgbyHjv-HLZqtVYYZ4lMg/edit CLs in this series: https://crrev.com/c/2878175 Update NEL browser tests to require Report-To https://crrev.com/c/2878376 Separate parsing from processing Reporting-Endpoints https://crrev.com/c/2889833 Add reporting source to worker objects https://crrev.com/c/2889975 Add reporting source to COOP/COEP reporters https://crrev.com/c/3039579 Add source token to reports https://crrev.com/c/3041880 Add source token to IPC calls https://crrev.com/c/3042463 Isolate v1 reports from each other https://crrev.com/c/3042465 (This CL) Allow document source token to change https://crrev.com/c/3042521 Clean up when docs/workers are destroyed Bug: 1062359 Change-Id: I908e49b7b773c57335f8c527843643c896082ce4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3042465 Commit-Queue: Ian Clelland <iclelland@chromium.org> Reviewed-by: Matt Menke <mmenke@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Reviewed-by: Lily Chen <chlily@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/main@{#914491}
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:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If 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.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.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 wpt.live and w3c-test.org.
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!