← back to v153 · immersive-audio-model-and-formats-iamf-decoding-support
conformance · v153
v153 · immersive-audio-model-and-formats-iamf-decoding-support — 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-source-extensions-available |
The path this feature is delivered through: IAMF decoding is exposed to media elements via MSE, so without it there is nothing to add support to. spec ↗ | typeof | … | |
the-support-probe-itself-works |
The control every other assertion here depends on: a codec this browser certainly has must come back supported, and an invented one must not. Without both, a negative result about IAMF says nothing. spec ↗ | script | … | |
iamf-is-decodable-through-media-source |
The feature: an IAMF stream with Opus substreams is accepted by Media Source Extensions, so an adaptive player can offer it as a representation. spec ↗ | script | … | |
iamf-is-decodable-in-a-media-element |
The other half: canPlayType must recognise the same string, because that is what a <source> element's type attribute is checked against. MSE support without element support would leave plain markup unable to use it. spec ↗ | script | … | |
media-capabilities-reports-on-iamf |
decodingInfo is the only API that says whether playback will keep up and whether hardware is involved. For a format whose whole point is many substreams, that answer matters more than a boolean. spec ↗ | script | … | |
a-source-type-decides-before-any-request |
The mechanism a fallback ladder depends on: a <source> element's type attribute is checked with canPlayType, and an empty answer means the element moves on without requesting the file. Asserted here through canPlayType rather than by building an element and watching the network, because a conformance suite runs on every page of the feature and a probe that fetches a URL logs an error on all of them. The fetch-level proof lives in the fallback-ladder demo, where the requests are expected and explained. spec ↗ | script | … |