I accidentally posted this topic twice (once from my @google.com account, and again from my @chromium.org account), so I'll re-post your question in the thread originating from my @chromium.org account and respond there, sorry for the confusion!
On Thu, Oct 21, 2021 at 10:59 AM David Baron <[email protected]> wrote: > The spec <https://www.w3.org/TR/mediaqueries-5/#dynamic-range> requires > that "The combination of the User Agent and the output device fulfill all > of the following criteria" when describing what it means to be high > dynamic-range. Since Chromium doesn't support wide-gamut colors in CSS, > HTML, or Canvas, I think it's probably incorrect to report that > (dynamic-range: > high) is true based only on the device, which is what it looks to me like > the current code > <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/css/media_query_evaluator.cc;l=351-378;drc=4d3cb20c1aebba55e54112531222c7434d29f3b0> > does. Admittedly, the spec could probably use some clarification as to > what it means for the User Agent to fulfill the criteria for both the > dynamic-range and video-dynamic-range queries, but my understanding of > what the spec is trying to say is that Chrome probably shouldn't say that > (dynamic-range: > high) is true until it supports wide-gamut colors in at least some and > maybe all of those contexts. > > -David > > On Wed, Oct 20, 2021 at 11:41 AM 'Will Cassella' via blink-dev < > [email protected]> wrote: > >> Contact [email protected], [email protected], >> [email protected] >> >> Explainer >> Adds MediaQueries for detecting HDR vs HDR displays >> https://www.w3.org/TR/mediaqueries-5/#dynamic-range >> https://www.w3.org/TR/mediaqueries-5/#video-dynamic-range >> >> Specificationhttps://www.w3.org/TR/mediaqueries-5/#dynamic-range >> >> Summary >> >> Adds media queries to CSS which allow a page to detect the current >> display device’s support for HDR. This feature adds two new CSS media >> queries: 'dynamic-range' and 'video-dynamic-range', both of which may be >> one of 'standard' or 'high'. Chrome will resolve these queries according to >> the capabilities of the display device the browser window is currently >> positioned on, allowing pages to toggle CSS rules accordingly or respond in >> Javascript via 'window.matchMedia()'. >> >> >> Blink componentBlink>CSS >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> >> >> Motivation >> >> As HDR-supported displays become more common, web developers need ways to >> enable HDR content on their web pages without compromising the experience >> for users of non-HDR displays, or mixed-HDR multi-display setups. CSS >> already provides the 'media query' concept for toggling rules based on >> display device characteristics, and this feature extends that set of >> queries to enable detecting HDR support on the current display device. >> >> >> Initial public proposal >> >> TAG reviewNot Filed. This is an incremental change to CSS Media Queries, >> already adopted by CSS WG. >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> >> >> Gecko: Worth prototyping ( >> https://github.com/mozilla/standards-positions/issues/584) >> >> WebKit: Shipped/Shipping ( >> https://webkit.org/blog/10247/new-webkit-features-in-safari-13-1/) >> Partially implemented - `video-dynamic-range` not yet supported >> >> Web developers: Positive ( >> https://github.com/w3c/csswg-drafts/issues/4471#issuecomment-548085935) >> Feature designed with the help of Netflix. >> >> >> Debuggability >> >> No specific DevTools support >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >> ?Yes >> https://wpt.fyi/results/css/mediaqueries/dynamic-range.html >> >> Flag nameCSSDynamicRangeMediaQueries >> >> Requires code in //chrome?False >> >> Tracking bughttps://crbug.com/1224711 >> >> Estimated milestones97 >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5680926106320896 >> >> This intent message was generated by Chrome Platform Status >> <https://www.chromestatus.com/>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKj4DkD1-oS5OSZye8DwcGhdrYVwKYv3omYOwE0p-WCm3L77iw%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKj4DkD1-oS5OSZye8DwcGhdrYVwKYv3omYOwE0p-WCm3L77iw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "blink-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/a/chromium.org/d/topic/blink-dev/OpUsOWnnN6c/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG0MU3gHMxyCBxWphPTg4mP8RNbsJQC30pAaB4-P4%3D-FLA4B0w%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG0MU3gHMxyCBxWphPTg4mP8RNbsJQC30pAaB4-P4%3D-FLA4B0w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BF%3DP4gSPuuBLrt%2BvJQeqhB1hwttV7QNk%2B-99eUzgYU0%3DrAEqg%40mail.gmail.com.
