| commit | a57b6bdf00987cf820d34e268779232d1aea8709 | [log] [tgz] |
|---|---|---|
| author | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Apr 10 17:58:07 2024 |
| committer | GitHub <noreply@github.com> | Wed Apr 10 17:58:07 2024 |
| tree | f664149025f1c675e85235108c3a45594838d8e1 | |
| parent | 2c7c60f2f062e2fd55cffaab4b2b5dbdd9c67ada [diff] |
Reland "Cross-origin support for window.fence.reportEvent()." (#45554) This is a reland of commit 280fe80c08b919b9cb7ba8228b1b0323ce5bceea. There is a known flakiness issue with tests that involve loading cross-origin subframes with remote context executors. The way we historically have fixed that is by splitting up each promise_test into a separate file. This CL attempts to fix that flakiness by doing just that. Original change's description: > Cross-origin support for window.fence.reportEvent(). > > Third-party ad serving (3PAS) lets advertisers manage ads across > different bidding platforms. However, the event-level reporting API > (reportEvent()) currently prevents direct reporting from documents > that are cross-origin to the root ad frame's fenced frame config's > mapped URL, limiting this functionality for the 3PAS use case. This CL > extends the reportEvent() API to support this use case. > > To allow cross-origin reporting while still preserving privacy, both > the ad frame and the 3PAS subframe must explicitly opt in. The ad > frame opts in using a new `Allow-Cross-Origin-Event-Reporting` > response header, while the 3PAS subframe opts in by calling > reportEvent() with `crossOriginExposed=true`. If both opt-ins are > present, then the reportEvent() call from the 3PAS document will > succeed. > > This CL adds histograms to track how many beacons are sent from > documents that are same-origin and cross-origin to the fenced frame > config's mapped url. > > This CL also expands the fenced frame WPT system to support > content-initiated navigations of fenced frame contexts to cross-origin > URLs. > > Change-Id: I4e895bec4cb77604e2017cfc67b496d59863a30b > Bug: 331844131 Bug: 331844131 Change-Id: Iacf17786ba5471faff15252c87e1924698ab4583 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5425335 Reviewed-by: Dominic Farolino <dom@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Tarun Bansal <tbansal@chromium.org> Commit-Queue: Liam Brady <lbrady@google.com> Cr-Commit-Position: refs/heads/main@{#1283165} Co-authored-by: Liam Brady <lbrady@google.com>
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!