← back to v150 · opaque-origin-for-data-urls
conformance · v150
v150 · opaque-origin-for-data-urls — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
worker-constructor-exposed |
Worker is exposed on the global — the surface this rule applies to. | exists | … | |
sharedworker-constructor-exposed |
SharedWorker is exposed (where supported); the data: rule applies symmetrically. | script | … | |
data-url-worker-launchable |
new Worker("data:text/javascript,...") can be constructed without synchronous throw — the security-origin change is observed at runtime, not at construction. | script | … | |
data-url-worker-cannot-access-origin-credentials |
A worker created from a Blob URL reports its location.origin via postMessage; the round-trip is observable, demonstrating the worker boundary is intact. spec ↗ | script | … | |
data-url-fetch-still-supported |
fetch("data:...") still resolves — only the inherited security origin for workers changed. | script | … |