← back to v158 · resource-timing-get-encoded-decoded-body-size-with-cors-instead-of-tao

conformance · v158

v158 · resource-timing-get-encoded-decoded-body-size-with-cors-instead-of-tao — conformance probe

6 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.

browser: … spec: https://w3c.github.io/resource-timing/ chromestatus: #5195340595724288 generated 2026-10-04T10:00:00Z by misc-builder
0
pass
0
fail
0
blocked
6
total
id contract kind verdict detail
body-size-attributes-exist PerformanceResourceTiming exposes encodedBodySize, decodedBodySize and transferSize. spec ↗ script …
same-origin-sizes-exposed A same-origin fetch always exposes non-zero encoded and decoded body sizes for a non-empty response — no gate applies. spec ↗ script …
cors-exposes-body-sizes-without-tao A cross-origin resource fetched with CORS (ACAO present, no Timing-Allow-Origin) exposes encoded/decoded body sizes — the new CORS gate. Requires network access to raw.githubusercontent.com; a fetch error fails with its detail. spec ↗ script …
tao-only-opaque-sizes-hidden An opaque (no-cors) response no longer exposes body sizes even when it carries Timing-Allow-Origin: * — TAO alone stops being the body-size gate. Requires network access to cdn.jsdelivr.net. spec ↗ script …
transfersize-needs-both-gates transferSize stays 0 for a CORS response without Timing-Allow-Origin — under the new rules it requires both opt-ins. Requires network access to raw.githubusercontent.com. spec ↗ script …
responsestatus-follows-cors-precedent responseStatus, the precedent CORS-gated attribute this change aligns with, is exposed for a CORS response regardless of TAO. Requires network access to raw.githubusercontent.com. spec ↗ script …