← back to v146 · cpu-performance-api
conformance · v146
v146 · cpu-performance-api — 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 |
|---|---|---|---|---|
navigator-cpuperformance-exists |
navigator.cpuPerformance is exposed as a property on the Navigator interface. spec ↗ | script | … | |
navigator-cpuperformance-is-number |
navigator.cpuPerformance returns a number (the unsigned short performance tier). | script | … | |
cpuperformance-tier-in-known-range |
The reported tier is an integer in 0..4 (0 = unknown, 1..4 = increasing capability); future tiers >4 may be returned but a number is always present. spec ↗ | script | … | |
cpuperformance-readonly |
navigator.cpuPerformance is readonly — assigning to it does not change the read-back value. | script | … | |
no-raw-cpu-fingerprint-fields |
Only the coarse tier is exposed — there is no navigator.cpuModel, navigator.cpuCoreCount, or similar raw identifier on Navigator. | script | … | |
hardwareconcurrency-still-available |
navigator.hardwareConcurrency remains the legacy core-count signal; the new tier supplements rather than replaces it. | typeof | … |