commit | 7f9790cd8ab7c20a975a15b1b07e049588a28126 | [log] [tgz] |
---|---|---|
author | Etienne Noel <etiennenoel@google.com> | Tue Nov 08 19:24:41 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Nov 08 19:39:18 2022 |
tree | 554fe95d6b6c4fbe7878eaed3b8453cafb35c513 | |
parent | 1f0797d9413a563b9bdb95d7eed9988cf8aa2211 [diff] |
CacheStorage now keeps the fragment in the Request URL but doesn't save it in the Cache key. The Cache storage now keeps in the Request Metadata, the complete URL (including the fragment). However, when doing the match, the fragment part is removed. This means that these 3 example URLs will all match: https://example.com/path https://example.com/path#ref https://example.com/path#ref2 The latest url put in the cache will be the one saved and returned in the Request. The specifications (https://w3c.github.io/ServiceWorker/#request-matches-cached-item-algorithm) states that the cached URL should be the request URL and no where is it specified that the fragment should be removed from the cachedURL: "Let cachedURL be request’s url" However, it is specified that during matching, the fragment should be excluded: "If queryURL does not equal cachedURL with the exclude fragment flag set". ---- This CL modified the following: - `third_party/blink/renderer/core/fetch/request.h` The `removeFragment` parameter was added to the `CreateFetchAPIRequest( bool removeFragment = true)` and by default, for retro-compatibility reasons, the fragment is removed. Once we are certain that always keeping the fragment doesn't cause any side-effects, we can change this behaviour and just remove the code that was removing the fragment. - Methods to support manipulating fragments (ref) and their unit tests were also added. - The cache now saves the url in the request metadata so modifications to the proto file were made. Bug: 1205111 Change-Id: Ib23fd5a9364bc64159a2859dc9fd9d3512697202 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3859817 Reviewed-by: Charlie Harrison <csharrison@chromium.org> Commit-Queue: Etienne Noël <etiennenoel@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Reviewed-by: Oriol Brufau <obrufau@igalia.com> Reviewed-by: Maks Orlovich <morlovich@chromium.org> Reviewed-by: Finnur Thorarinsson <finnur@chromium.org> Reviewed-by: Yaron Friedman <yfriedman@chromium.org> Reviewed-by: Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/main@{#1068711}
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!