commit | ee8a5d646573cfdcae3c95c5543209d17affd47c | [log] [tgz] |
---|---|---|
author | Ming-Ying Chung <mych@chromium.org> | Fri Nov 10 09:01:57 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 10 09:01:57 2023 |
tree | 56f42deadeb6a11a10ac17c06ec1601ebbb6ff02 | |
parent | 0a91c9026b5268939b2f3e229a526b879bd35040 [diff] |
Update fetch keepalive WPT helper 1. Updated `assertStashedTokenAsync()` as pointed out in [1] that it may not properly wait until token is fetched. Also added more error msg. This leads to issues fixed by (4) below. 2. Renamed `disallowOrigin` to `disallowCrossOrigin` to make it clear. 3. In keepalive-related tests, renamed the arg `shouldPass`: - for `assertStashedTokenAsync()`: `expectTokenExist` - for other references in tests: `expectFetchSucceed` 4. Fixed `stash-put.py` which didn't handle `cors` / `no-cors` requests properly. Previously: - for `cors` request without `disallow_cross_origin`, it still stores the token; however it should not. - for `no-cors` request, there was no special treatment; after this CL, it should always store the token no matter `disallow_cross_origin` is provided or not. 5. Extended `keepaliveRedirectTest()` to support the case without unloading its iframe. [1]: https://crrev.com/c/4988570/11/third_party/blink/web_tests/external/wpt/fetch/api/redirect/redirect-keepalive.https.any.js#20 Bug: 1356128 Change-Id: I72926789ac3af7ee7d04dc95128f2685d7d21df2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5014033 Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Ming-Ying Chung <mych@chromium.org> Cr-Commit-Position: refs/heads/main@{#1222812}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.