← back to v143 · fedcm-privacy-enforcement-for-client-metadata
conformance · v143
v143 · fedcm-privacy-enforcement-for-client-metadata — 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 |
|---|---|---|---|---|
identity-credential-exposed |
IdentityCredential interface remains exposed. spec ↗ | exists | … | |
credentials-get-is-function |
navigator.credentials.get is the entry point for FedCM flows including ones using client_metadata. spec ↗ | typeof | … | |
fedcm-requires-secure-context |
FedCM is gated to secure contexts — IdentityCredential is undefined on http: pages. spec ↗ | script | … | |
fedcm-config-rejects-bad-url |
navigator.credentials.get returns a Promise even with an invalid configURL (no synchronous throw). spec ↗ | script | … | |
fedcm-respects-abort-signal |
FedCM call returns a Promise that respects AbortSignal aborts (privacy enforcement still cancellable). spec ↗ | script | … | |
well-known-web-identity-fetch |
fetch() exists so the .well-known/web-identity document can be probed for direct endpoints. spec ↗ | typeof | … |