- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Oct 2023 20:08:48 +0000
- To: public-css-archive@w3.org
Regarding `prefers-reduced-data`, I'd say, the opposite use case is probably the more important one. Imagine, a user loads a page and sees that it drains their data So they turn reduced data _on_. In that case, the user probably expects the change to take effect immediately and further data transfer is reduced. `scripting` is a special case, as turning scripting on or off _requires_ a page reload to take effect on the JavaScript side. So CSS should follow that. Other media features like `prefers-color-scheme`, `prefers-contrast` or `pointer` seem to me like they should also take effect immediately when changed, because those changes can happen dynamically. And media features like `update`, `dynamic-range`, `color-gamut` or `resolution` are bound to the hardware and therefore mostly won't change dynamically. Given that, I'd suggest to add an entry to the definition table of each media feature that indicates whether UAs are expected to adjust to changes immediately or not. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9475#issuecomment-1767092565 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 October 2023 20:08:49 UTC