Navigation-Timing: destination-based TAO#60823
Conversation
This CL implements whatwg/html#12513 and whatwg/fetch#1931, in order to resolve w3c/navigation-timing#215. It enables developers to opt-in to get cross-origin redirect timings, through destination-based Timing-Allow-Origin headers. I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/GOPn8-wQlsk/m/x5Q3G6KuAgAJ Change-Id: Ib463010f1862af523a241d2e9180ff09bfedb101 Bug: 521861828 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7915892 Commit-Queue: Yoav Weiss (@Shopify) <yoavweiss@chromium.org> Reviewed-by: Noam Rosenthal <nrosenthal@google.com> Cr-Commit-Position: refs/heads/main@{#1650808}
18f1e89 to
61c7e8d
Compare
wpt-pr-bot
left a comment
There was a problem hiding this comment.
The review process for this patch is being conducted in the Chromium project.
Uh oh! Looks like an error!Client ID static/taskcluster/github does not have sufficient scopes and is missing the following scopes: This request requires the client to satisfy the following scope expression:
|
Uh oh! Looks like an error!Client ID static/taskcluster/github does not have sufficient scopes and is missing the following scopes: This request requires the client to satisfy the following scope expression:
|
|
@foolip - can you take a look at this? AFAICT, the firefox flake is unrelated, as it seems to be failing at a test where the only thing this PR changed is the expectation in one of the other test cases. |
|
@jcscottiii - As @foolip is OOO, he sent me your way. Can you take a look? |
|
@yoavweiss I believe you're right. We will retrigger this. If it still fails, we can force merge. |
Timing-Allow-Origin (TAO) currently only opts-in "backwards" in terms of origins and doesn't constitute an opt-in to the destination origin, which is the appropriate opt-in for navigations (contrary to subresources). This PR adds the mechanisms that can enable such "forward" opt-in, and can enable a navigation response to a redirect chain to know that the redirect chain opted in to expose the redirects to its origin. Tests: web-platform-tests/wpt#60823 & web-platform-tests/wpt#60873. Corresponding HTML PR: whatwg/html#12513.
This CL implements whatwg/html#12513 and
whatwg/fetch#1931, in order to resolve
w3c/navigation-timing#215.
It enables developers to opt-in to get cross-origin redirect timings,
through destination-based Timing-Allow-Origin headers.
I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/GOPn8-wQlsk/m/x5Q3G6KuAgAJ
Change-Id: Ib463010f1862af523a241d2e9180ff09bfedb101
Bug: 521861828
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7915892
Commit-Queue: Yoav Weiss (@Shopify) <yoavweiss@chromium.org>
Reviewed-by: Noam Rosenthal <nrosenthal@google.com>
Cr-Commit-Position: refs/heads/main@{#1650808}