← back to v149 · inline-script-cache
conformance · v149
v149 · inline-script-cache — 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-observer-exists |
PerformanceObserver exists so visitors can observe script compile/eval timing. | exists | … | |
supports-resource-entry-type |
PerformanceObserver.supportedEntryTypes reports the 'resource' entry type used to measure scripts. | script | … | |
supports-navigation-entry-type |
PerformanceObserver.supportedEntryTypes reports the 'navigation' entry type, which carries page-level scripting timing in supporting browsers. | script | … | |
performance-getentries-callable |
performance.getEntriesByType returns an array, used by callers to inspect script-load timing. | script | … | |
inline-script-executes-synchronously |
Inline classic <script> elements execute synchronously, the precondition for inline-script bytecode caching to be observable. | script | … | |
navigation-timing-type-on-entry |
PerformanceNavigationTiming entries expose a .type property, the field used by code that tracks cold-vs-warm loads. | script | … |