commit | cf9a213635193035a3409436a594995e84e5346d | [log] [tgz] |
---|---|---|
author | Hayato Ito <hayato@chromium.org> | Mon Feb 15 04:24:59 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Feb 15 04:43:14 2021 |
tree | f7cdafb4b87118b355288a4cdb5e6af2c467842d | |
parent | 17439a93d434f9af5009c5144129f8dadf93323b [diff] |
Support a crossorigin= attribute for webundle subresource loading There are several changes in this CL. Let me summarize at first. The current behavior is: - No support crossorigin= attribute - request's mode is set to "cors" in default. - request's creditial-mode is "omit"; UA never sends a credential. This CL changes the behavior as follows: - If crossorigin= attribute is not specified, - request's mode is set to "no-cors" - request's credential-mode is set to "include" - If crossorigin= attribute is "anonymous" or empty (See [1] for details) - request's mode is set to "cors" - request's credential-mode is set to "same-origin" - If crossorigin= attribute is "use-credential", - request's mode is set to "cors" - request's credential-mode is set to "include" Note: In the current implementation, subresources can be loaded from a cross-origin bundle which the server returns without a valid "Access-Control-Allow-Origin" response header. That should be considered as a bug. This Cl changes request's mode to no-cors correctly in default. Regarding tests, A general behavior of a crossorigin attribute is well tested in existing tests, such as fast/dom/HTMLLinkElement/link-crossOrigin.htm. This CL tests only the effects of crossorign= attributes for a bundle as follows: 1. Test for credentials: subresource-loading-credential.tentative.sub.html 2. Test for CORS behavior: subresource-loading-cors.tentative.html 3. Test for CORS behavior (error case): subresource-loading-cors-error.tentative.html The existing test, subresource-loading-cross-origin.tentative.html is rewritten and split into 2 and 3. Due to https://crbug.com/1168449, the test 3 is marked as TIMEOUT. This bug will be fixed as another CL. [1]: https://html.spec.whatwg.org/multipage/#cors-settings-attribute BUG=1149816, 1168449 Change-Id: I354e203a3a536bc829ef7ba6a97d4edd6a6340a0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2670486 Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Hayato Ito <hayato@chromium.org> Cr-Commit-Position: refs/heads/master@{#853942}
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.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 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.
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!