| commit | 2c1f4d078ea2f745a1cacf3bca6ce1153373784a | [log] [tgz] |
|---|---|---|
| author | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Oct 13 23:46:36 2022 |
| committer | GitHub <noreply@github.com> | Thu Oct 13 23:46:36 2022 |
| tree | 2a2f6f6a5614a2032d05742539a233b24e75d9ee | |
| parent | b2c0c53477ebe43606de065fcb91f782f374287b [diff] |
Navigation rewrite: Add WPT for initiator origin in document state (#36352)
Per one of the remaining work items [1] in the navigation & session history spec rewrite, we need to store the original initiator origin of a given session history entry's document state.
This CL introduces a test to ensure that the initiator origin in a document state is indeed used in history navigations. The way we test this is by:
1.) Producing a session history of [A] -> [B], in order to set [B]'s initiator origin to [A] (also we disable bf-cache). [A] and [B] are cross-site
2.) Navigate back to [A] ([B] is destroyed), and perform location.replace([B])
3.) Then perform history.forward() to initiate a same-origin history navigation to a session history entry whose document state has a cross-origin initiator origin
4.) Confirm that the history.forward() [B] loads with request parameters consistent with the document state that captures state from the *original* initiator. For example:
- Sec-Fetch-Site: cross-site, implying that the initiator origin was
saved to the document state and correctly re-used upon subsequent
navigation (even by a same-origin document).
- Referer: cross-origin, implying that it was correctly written to
the document state the first time, and reused later
- document.referrer (same as above)
[1]: https://docs.google.com/document/d/1yxnzjRDVmAR5CC9GcAyY448lBD0u0E98eUEMHDhx1Dw/edit#heading=h.lwfczldtst3r
R=domenic@chromium.org
Bug: N/A
Change-Id: I2361ef7d5d516e71ad3026626db97a5b9fdb8e38
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3936785
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1056900}
Co-authored-by: Dominic Farolino <dom@chromium.org>
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!