← back to v148 · content-type-in-resource-timing
conformance · v148
v148 · content-type-in-resource-timing — 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 |
|---|---|---|---|---|
performance-resource-timing-exists |
PerformanceResourceTiming is the interface the contentType field is added to. spec ↗ | exists | … | |
content-type-on-prototype |
PerformanceResourceTiming.prototype defines a contentType getter. spec ↗ | script | … | |
supported-entry-types-resource |
'resource' remains in PerformanceObserver.supportedEntryTypes. spec ↗ | script | … | |
get-entries-by-type-resource |
performance.getEntriesByType('resource') returns an array of resource entries. spec ↗ | script | … | |
content-type-is-string |
When a resource entry exists, its contentType is a string (possibly empty when TAO is not granted). spec ↗ | script | … | |
same-origin-css-content-type-entry |
A same-origin fetch for a CSS resource produces a resource timing entry whose contentType matches the server Content-Type. spec ↗ | script | … |