← back to v152 · mediacapabilities-decodinginfo-encryptionscheme
conformance · v152
v152 · mediacapabilities-decodinginfo-encryptionscheme — 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 |
|---|---|---|---|---|
media-capabilities-exists |
navigator.mediaCapabilities is exposed. spec ↗ | exists | … | |
decoding-info-is-function |
decodingInfo() is callable. spec ↗ | typeof | … | |
decoding-info-answers-clear-content |
decodingInfo() resolves with a boolean supported field for an unencrypted H.264 query. spec ↗ | script | … | |
key-system-configuration-accepted |
decodingInfo() accepts a keySystemConfiguration dictionary naming Clear Key — the EME-mandatory common key system — and resolves with a boolean answer. Any rejection fails: Clear Key must be available on every EME-supporting browser, so a rejection here is a real conformance failure, not an acceptable device state. spec ↗ | script | … | |
unrecognized-scheme-refused |
The core v152 contract: with encryptionScheme set to an unrecognized value, an implementing browser must answer supported: false for a configuration it can otherwise decode (a browser that ignores the member answers true and fails; a device with no decodable baseline codec reports failure as indeterminate). spec ↗ | script | … | |
cenc-scheme-query-resolves |
A 'cenc' encryptionScheme query against Clear Key resolves to a boolean answer (true and false are both valid device capabilities). Any rejection fails: Clear Key is the EME-mandatory common key system, so this query must be answerable on a conformant browser. spec ↗ | script | … |