← back to v150 · algorithm-updates-in-webcrypto

conformance · v150

v150 · algorithm-updates-in-webcrypto — conformance probe

8 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.

browser: spec: https://wicg.github.io/webcrypto-modern-algos chromestatus: #5198951632470016 generated 2026-07-24T18:10:00Z by kimi-k3-manual-iteration
0
pass
0
fail
0
blocked
8
total
id contract kind verdict detail
subtlecrypto-encapsulatekey-method crypto.subtle.encapsulateKey is a function — KEM encapsulation producing an EncapsulatedKey (sharedKey CryptoKey + ciphertext). spec ↗ typeof
subtlecrypto-encapsulatebits-method crypto.subtle.encapsulateBits is a function — KEM encapsulation producing raw shared-secret bits + ciphertext. spec ↗ typeof
subtlecrypto-decapsulatekey-method crypto.subtle.decapsulateKey is a function — reverses encapsulation to a shared-secret CryptoKey. spec ↗ typeof
subtlecrypto-decapsulatebits-method crypto.subtle.decapsulateBits is a function — reverses encapsulation to raw bits. spec ↗ typeof
subtlecrypto-getpublickey-method crypto.subtle.getPublicKey is a function — derives the public CryptoKey from an asymmetric private key with chosen usages. spec ↗ typeof
subtlecrypto-supports-static The static SubtleCrypto.supports exists on the interface object — the spec's feature-detection method, shipped in Chromium under the same RuntimeEnabled=WebCryptoPQC gate (subtle_crypto.idl). spec ↗ typeof
secure-context-gate The partial SubtleCrypto interface is [SecureContext]: on a non-secure context the new methods must be absent (on a secure context either state is spec-legal, since the runtime feature also gates them). spec ↗ script
supports-returns-boolean-for-registered-name When the static interface method is present, SubtleCrypto.supports('generateKey', 'ML-KEM-768') — a name registered in spec section 6.2 — answers with a real boolean (never undefined/throw), so callers can rely on it before attempting key generation. spec ↗ script