- From: Christopher Cameron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2025 22:57:23 +0000
- To: public-css-archive@w3.org
It'll be good to discuss in person at the F2F (I'll be calling in though). Yes, the actually used HDR limit is affected by lots of factors, and part of the goal with the `standard`, `constrained-high`, `high` division is to give the user agent the freedom to make these sorts of choices. So in the example, suppose you have an XDR display with headroom 16x. There is an video that would actually use the full 16x headroom. The user agent is free to look at the layout of the page and say "I'm going to say that `high` actually means 4x, because of (various heuristics)". And if the user agent later sees that the video is fullscreen (or mostly-fullscreen) it san say "let's kick `high` up to mean 16x". It sounds like there's another separate feature swirling around which is a signal to say "do whatever is possible to give the maximum available headroom, because I really want it". It vaguely reminds me of https://github.com/w3c/screen-wake-lock/issues/129#issuecomment-817151517 ... but it's not quite the same. It's sort-of a permission issue because it's saying "discard your power preferences, etc". -- GitHub Notification of comment by ccameron-chromium Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11558#issuecomment-2608436457 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 January 2025 22:57:24 UTC