← back to v151 · chrome-will-remove-support-for-macos-12
conformance · v151
v151 · chrome-will-remove-support-for-macos-12 — 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 |
|---|---|---|---|---|
user-agent-string-exposed |
navigator.userAgent is exposed so the platform string can be read; this is the surface Chrome used to communicate the OS deprecation infobar trigger. | typeof | … | |
user-agent-data-platform-exposed |
navigator.userAgentData.platform exposes the OS name used by deprecation-targeted features. Chrome exposes this; other browsers may not. | script | … | |
high-entropy-platform-version-available |
navigator.userAgentData.getHighEntropyValues() resolves with a platformVersion string — the field Chrome reads to detect macOS 12 builds that fall outside the support window. | script | … | |
platform-string-not-empty |
navigator.platform is non-empty so legacy macOS detection paths keep working for the warning infobar period. | script | … | |
chrome-version-token-present |
The user-agent contains a Chrome/<version> token so server-side feature gates can detect Chrome 151+ rejections of macOS 12 hosts. | script | … |