On Thu, Oct 21, 2021 at 7:01 AM Will Cassella <[email protected]> wrote:
> Thanks for the feedback! I've updated that section: > > Debuggability > > Styles with these media queries can be viewed and edited in the devtools > frontend, albeit without proper highlighting. I've created pull requests on > the relevant libraries used in the devtools frontend to enable this. > https://github.com/stylelint/stylelint/pull/5613 > https://github.com/codemirror/CodeMirror/pull/6803 > > On Wednesday, October 20, 2021 at 9:10:36 AM UTC-7 Mathias Bynens wrote: > >> On Wed, Oct 20, 2021 at 5:44 PM Will Cassella <[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. >>> >> I agree a TAG review is not needed for the `dynamic-range` MQ, as it's shipped in Safari and adopted by the CSSWG. The video variant however doesn't meet that criteria. Was the concept of `video-*` MQs discussed with the TAG? Are there other `video-*` MQs that are already shipped? > >>> >>> 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 >>> >> >> Please follow https://goo.gle/devtools-checklist and elaborate on this a >> little bit. Per the guide, we need to ensure DevTools supports basic >> editing of this new media query. It looks like this works out of the box in >> Canary. >> >> >>> 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/CA%2BF%3DP4hQtag7Ja_7HF4jRHbuC8h5-_0TzjoJvVEMHmrUeZYW9g%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BF%3DP4hQtag7Ja_7HF4jRHbuC8h5-_0TzjoJvVEMHmrUeZYW9g%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/6655cbcd-90a1-4b34-a332-5adeada4b53fn%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6655cbcd-90a1-4b34-a332-5adeada4b53fn%40chromium.org?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/CAL5BFfWFhKO4m-Ae3_XSRSMEDvYDTHctU5nGHBkiKyytN9k0FQ%40mail.gmail.com.
