video-dynamic-range Media Query
#508
Comments
|
@lukewarlow can you say something about the use cases for this, why it's important? Is it mainly to be able to use in |
|
cc @dalecurtis |
|
w3c/csswg-drafts#4471 I think the summary at the top of this gives a pretty good explanation of the reason to have the two media queries and then yeah it'd mostly be used like you suggest choosing different media based on support. |
|
Thank you for proposing We wanted to let you know that this proposal was not selected to be part of Interop this year. This proposal was not included in Interop 2024 because when we looked at its Web Platform Tests results, we found that it is already largely interoperable between tested browsers and does not need special coordinated attention. For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024! Posted on behalf of the Interop team. |
Description
Following on from Interop 2023s Media Queries 4 focus area, it would be good for some of Media Queries 5 to be focussed on next. This request is specifically for the
video-dynamic-rangemedia query, this has shipped in Firefox but not Chromium or WebKit.Specification
https://drafts.csswg.org/mediaqueries-5/#video-dynamic-range
Open Issues
No response
Tests
https://wpt.fyi/results/css/mediaqueries/dynamic-range.html
Current Implementations
Standards Positions
No response
Browser bug reports
WebKit Bug: https://bugs.webkit.org/show_bug.cgi?id=249678
Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1224711
Developer discussions
No response
Polls & Surveys
No response
Existing Usage
No response
Workarounds
No response
Accessibility Impact
No response
Privacy Impact
This exposes a new fingerprinting bit, but I don't think much more than what's already exposed by
dynamic-rangeOther
No response
The text was updated successfully, but these errors were encountered: