← back to v139 · fire-error-event-instead-of-throwing-for-csp-blocked-worker
conformance · v139
v139 · fire-error-event-instead-of-throwing-for-csp-blocked-worker — 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.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
worker-exposed |
Worker constructor is exposed. | typeof | … | |
shared-worker-exposed |
SharedWorker constructor is exposed — also affected by the spec-aligned error-event behaviour. | typeof | … | |
addeventlistener-on-worker-prototype |
Worker.prototype exposes addEventListener so the async 'error' event delivered for CSP-blocked workers can be observed. | script | … | |
constructing-worker-does-not-throw-synchronously |
Per the spec change, constructing a Worker that will ultimately be CSP-blocked must not throw synchronously — the failure is delivered later via an 'error' event. We probe by trying a regular data: URL worker construction; it should not throw at construction time. spec ↗ | script | … | |
csp-violation-event-supported |
Document still fires SecurityPolicyViolationEvent for CSP violations — the error event on the worker complements (not replaces) the violation report. | exists | … | |
error-event-constructor |
ErrorEvent constructor is exposed; this is the interface dispatched on the worker when CSP blocks its fetch. | typeof | … |