← back to v151 · cross-origin-redirect-timing-opt-in
conformance · v151
v151 · cross-origin-redirect-timing-opt-in — conformance probe
4 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
4
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
resource-timing-redirectstart-exists |
PerformanceResourceTiming exposes redirectStart — the field a redirect chain populates and that Timing-Allow-Origin gates for cross-origin callers. spec ↗ | exists | … | |
resource-timing-redirectend-exists |
PerformanceResourceTiming exposes redirectEnd. spec ↗ | exists | … | |
same-origin-redirect-timing-exposed |
Following a same-origin redirect chain populates redirectStart/redirectEnd on the resource entry (redirectEnd >= redirectStart > 0), which is the timing the cross-origin opt-in unlocks via Timing-Allow-Origin. spec ↗ | script | … | |
timing-allow-origin-request-header-name |
The opt-in is the Timing-Allow-Origin response header; a Headers object accepts and preserves it (the mechanism a redirect hop must send to expose its timing cross-origin). spec ↗ | script | … |