commit | 617fa69a4969e0765590322112166388471783ed | [log] [tgz] |
---|---|---|
author | David Van Cleve <davidvc@chromium.org> | Thu Sep 23 02:11:51 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Sep 23 02:24:28 2021 |
tree | 33a8aacd66d03238893e984661a809a1462bee67 | |
parent | 4bffb947f356ab179f50e70bdf637262c6b0bb66 [diff] |
css: Use document (not base) URL for inline style preloads' referrers crrev.com/c/2592447 fixed one code path where setting a document's base URL (via the HTML <base> tag) led to requests from inline CSS using the base URL as their referrer, rather than the document URL. This goes against the recommendation in the Referrer Policy spec that requests from inline CSS use their documents' referrers. [1] In general, we try to avoid letting pages override outgoing requests' referrers to different-origin URLs, even though this is not a hard security boundary. It turns out a separate code path can also trigger requests from inline style sheets: in particular, '@import' statements in inline stylesheets get prefetched by the HTML parser, which currently has separate logic that explicitly sets those requests' referrers to the document's base URL. This change removes that logic. After this change, preload requests from inline style in the HTML parser will use the document's URL, not its base URL, when generating their referrers. This CL also adds two new WPTs: * "stylesheet-with-differentorigin-base-url.html" verifies the referrer for an inline stylesheet requesting another stylesheet via an @import statement. There are other tests inspecting the referrers for SVG and image fetches from inline stylesheets, but not for child stylesheet fetches. This test passes even without this CL applied (because of crrev.com/c/2592447). * "stylesheet-with-differentorigin-base-url-from-preload.html" does the same thing, except from a srcdoc iframe. Using a srcdoc iframe triggers the preload code path since the inline stylesheet is hardcoded in a <style> HTML tag. (In contrast, the test above uses JS to add the style element to the DOM.) Because this second test exercises the preload codepath, it fails without this patch's functional changes applied. With this patch applied, the repro in the linked bug no longer succeeds. [1] https://www.w3.org/TR/referrer-policy/#integration-with-css Test: New WPT covers the preload path. Manually tested the bug's repro. Change-Id: I6bd797978b207a4bc0bb1b35565eb93c7162729f Fixed: 1233375 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3078937 Commit-Queue: David Van Cleve <davidvc@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Emily Stark <estark@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Cr-Commit-Position: refs/heads/main@{#924146}
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!