- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 28 Jan 2015 13:13:33 -0800
- To: Rik Cabanier <cabanier@gmail.com>
- Cc: Mark Watson <watsonm@netflix.com>, "www-style@w3.org" <www-style@w3.org>
On Wed, Jan 28, 2015 at 12:26 PM, Rik Cabanier <cabanier@gmail.com> wrote: > On Wed, Jan 28, 2015 at 9:02 AM, Mark Watson <watsonm@netflix.com> wrote: >> It would be nice to be able to detect whether the display has the >> capability of rendering Wide Color Gamut and High Dynamic Range video. >> >> This is independent of codec support: in fact the video codec itself may >> be unaware of the colorspace and dynamic range of the encoded video. It may >> also be the case that the media pipeline in a device supports these things >> but the presently connected display does not. >> >> For WGC, the basic question is whether the display can interpret data >> coded in the BT.2020 or DCI P3 colorspaces (I say "interpret" deliberately, >> because I'm unaware of any displays that can render the full BT.2020 space >> yet.) >> >> Would it make sense to add attributes for these properties to the CSS OM >> View Module ? Other suggestions ? Questions ? > > What are you planning on doing with that information? > AFAIK it is defined that pages are composited in sRGB and then mapped to the > monitor profile. sRGB supports wide gamuts (at least theoretically). It's just outside the standard gamut, but still representable. > Would you use this to change color handling of a full-screen video? You can send different sources to <video> based on a media query. ~TJ
Received on Wednesday, 28 January 2015 21:14:20 UTC