← back to v145 · enabling-web-applications-to-understand-bimodal-performance-timings
conformance · v145
v145 · enabling-web-applications-to-understand-bimodal-performance-timings — 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 |
|---|---|---|---|---|
performance-exists |
performance is exposed — the global through which navigation timing confidence is read. | exists | … | |
navigation-entry-type-supported |
'navigation' is in PerformanceObserver.supportedEntryTypes — confidence is attached to PerformanceNavigationTiming. spec ↗ | script | … | |
navigation-timing-confidence-attribute |
PerformanceNavigationTiming.prototype exposes a confidence accessor — the new field describing the bimodal regime. spec ↗ | script | … | |
navigation-timing-confidence-on-entry |
An actual PerformanceNavigationTiming entry exposes a confidence value (object) for the current navigation. spec ↗ | script | … | |
navigation-timing-extends-resource-timing |
PerformanceNavigationTiming.prototype inherits the responseStart/loadEventEnd timings the confidence value is measured against. | script | … |