← back to v157 · expose-progressevent-in-service-workers

conformance · v157

v157 · expose-progressevent-in-service-workers — 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://xhr.spec.whatwg.org/#interface-progressevent chromestatus: #5069584943153152 generated 2026-09-24T13:40:00Z by showcase-opus-0mu-build
0
pass
0
fail
0
blocked
6
total
id contract kind verdict detail
progressevent-exposed-on-window ProgressEvent is a constructor on Window. This is the baseline the service-worker realm is being aligned with — it is the comparison point, not the feature. spec ↗ typeof …
progressevent-constructs-with-length-fields ProgressEvent accepts lengthComputable, loaded and total in its init dictionary and reads them back — the three attributes this feature names. spec ↗ script …
progressevent-exposed-in-dedicated-worker ProgressEvent is constructible inside a DedicatedWorkerGlobalScope. The worker builds one and reports its own result; the page does not infer it. spec ↗ script …
progressevent-exposed-in-service-worker THE FEATURE: ProgressEvent is exposed in ServiceWorkerGlobalScope and can be constructed there. A registered service worker constructs one and reports back over MessageChannel; nothing is inferred from the page's own realm. spec ↗ script …
progressevent-loaded-total-are-doubles-in-worker The values a worker reads off a ProgressEvent are JS numbers carrying fractional precision, per the IDL double type adopted in Chrome 136 — so a relay forwarding platform-constructed values inherits that precision instead of re-deriving it. spec ↗ script …
progressevent-length-not-computable-default lengthComputable defaults to false when the init dictionary omits it — the attribute that lets a relay say honestly that the server sent no content-length, rather than claiming a known total. spec ↗ script …