← back to v154 · expose-cssstylevalue-hierarchy-to-worker-contexts
conformance · v154
v154 · expose-cssstylevalue-hierarchy-to-worker-contexts — conformance probe
7 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
7
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
typed-om-exposed-to-window |
The baseline: all five interfaces are defined on Window. If this fails the harness is wrong, not the browser. spec ↗ | script | … | |
typed-om-exposed-to-a-dedicated-worker |
The feature itself: the same five interfaces must be defined inside a dedicated worker, per [Exposed=(Window, Worker, ...)]. Before Chrome 154 every one of them was undefined there. spec ↗ | script | … | |
cssunitvalue-constructs-inside-a-worker |
Being defined is not the same as being usable: the constructor must actually build a value with the right value and unit inside the worker. spec ↗ | script | … | |
cssstylevalue-parse-works-inside-a-worker |
Parsing is the operation that makes this worth having in a worker, and it must produce a CSSUnitValue rather than a string. spec ↗ | script | … | |
unit-conversion-works-inside-a-worker |
CSSNumericValue.to() is the parser's own unit conversion, and it is the reason a token pipeline can move off the main thread without reimplementing arithmetic. spec ↗ | script | … | |
typed-om-exposed-to-a-module-worker |
Module workers are Worker globals too, so the same exposure applies. spec ↗ | script | … | |
invalid-values-are-rejected-inside-a-worker |
The worker gets the real CSS parser, not a permissive one: a unitless number must be rejected for a length property. A regex fallback typically accepts it. spec ↗ | script | … |