- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Oct 2019 02:32:02 +0000
- To: public-css-archive@w3.org
My first instinct is that the most-CSS-y way to handle this would be through new video-* prefixed media features, although I don't know if there need to be as many new features as suggested. It sounds like most of the use cases would be covered by `video-resolution` and `video-color-gamut` (with values and interpretation equivalent to the [`resolution`](https://drafts.csswg.org/mediaqueries-4/#resolution) and [`color-gamut`](https://drafts.csswg.org/mediaqueries-4/#color-gamut) queries, but specifically for the video rendering pathway). I don't think we need to duplicate the legacy color-related queries. For rendering within a browser window, the width and height of the screen in CSS px would remain the same, only the dppx resolution would be different, so they wouldn't need separate queries. But for full screen video, the dimensions would be different. So maybe there would need to be `full-screen-video-width/height/aspect-ratio` queries. If that is necessary, it might be best to report the raw pixel counts (not CSS px), since that's what people are used to when talking about video resolution. However, this is also very similar to the dropped `device-width` and `device-height` queries, and I'm not sure why those were dropped & whether this would have the same problems. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4471#issuecomment-547712467 using your GitHub account
Received on Wednesday, 30 October 2019 02:32:04 UTC