HDR Media Capabilities

Main.HDRMediaCapabilities History

Hide minor edits - Show changes to output

Added lines 9-10:
* What is the state of `transition` support detection? https://github.com/w3c/media-capabilities/blob/main/explainer.md#transitioning-between-stream-configurations
 
Added line 8:
* on PS5, decodeInfo calls fail after more than 25 calls (synchronous or for the lifespan of the app?)
Changed lines 6-7 from:
* WebKit sights fingerprinting issues
 
to:
* WebKit sights fingerprinting issues (Chrome uses `powerEfficient: false` for configurations that require software decoding)
* Dolby needs to join the W3C to make and move proposals forward

 
Changed lines 11-13 from:
* Badging for DolbyVision profile 8 metadata usage requires decodeInfo to expose whether `hdrMetadataType` that maps to HLS SUPPLEMENTAL-CODECS attribute is supported (vs ignored).
to:
* Badging for DolbyVision profile 8 metadata usage requires decodeInfo to expose whether `hdrMetadataType` that maps to HLS SUPPLEMENTAL-CODECS attribute is supported (vs ignored). 
 
Should issue be filed here https://github.com/w3c/media-capabilities/issues ?
Added lines 1-10:
Image HDR support coming to Firefox?
 
MediaCapabilities implementations are missing features needed to check for feature/playback support on a variety of platforms.
 
* HDR fields currently ignored by Chrome (seems to be in the works https://chromium-review.googlesource.com/q/MediaCapabilities)
* WebKit sights fingerprinting issues
 
Example use-case
 
* Badging for DolbyVision profile 8 metadata usage requires decodeInfo to expose whether `hdrMetadataType` that maps to HLS SUPPLEMENTAL-CODECS attribute is supported (vs ignored).