Is there any signal from WebKit about video-* specifically? Also, are we assuming that the current issue on CSSWG <https://github.com/w3c/csswg-drafts/issues/5044> (and the implementation warning) about video-* numerical properties will have no impact on this? I.e., Is it just about the units or is there a chance that the whole video-* approach may be completely changed?
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 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/CADp2-T87%3DwjHw-M1TUHQTiPN26WyXijkxzcrO2XXezCHH8sY4g%40mail.gmail.com.
