← back to v147 · update-device-memory-api-limits
conformance · v147
v147 · update-device-memory-api-limits — 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-device-memory-exists |
navigator.deviceMemory is exposed. spec ↗ | exists | … | |
device-memory-type-number |
navigator.deviceMemory returns a number. spec ↗ | script | … | |
device-memory-within-bounds |
navigator.deviceMemory is greater than 0. spec ↗ | script | … | |
device-memory-valid-bucket |
navigator.deviceMemory returns a valid power-of-two or fraction bucket value (0.25, 0.5, 1, 2, 4, 8, 16, 32). spec ↗ | script | … | |
client-hint-echo-route-opts-in |
The memory-inspector echo endpoint opts in to Sec-CH-Device-Memory and varies on that request header. spec ↗ | script | … | |
client-hint-echo-reports-request-header |
The echo endpoint reports the actual Sec-CH-Device-Memory request header as a nullable value rather than simulating support. spec ↗ | script | … |