- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Oct 2023 01:21:05 +0000
- To: public-css-archive@w3.org
> Regarding prefers-reduced-data, I'd say, the opposite use case is probably the more important one. I agree. Turning that feature on on a page that is done dowloading heavy assets shouldn't throw these away to download additional lightweight assets. Overall, this concern was why we pushed back on having a `bandwidth` MQ, as this would dynamically change as the user goes in and out of rooms, tunnels… The expectation being that `preferred-reduced-data` is more of a semi-permanent setting, and as the occasional switch from one mode to the other is rare, it's not that much trouble. That said, we could add an explicit permission for the user to apply discretion as to the timing of the switch, making it clear that it's allowed to delay it on a per-page basis for as long as the user hasn't navigated elsewhere (or reloaded). I think that's kind of implied by the current definition (since the mechanism for turning it on or off is undefined), but we could be explicit. Or do we need to go further, and require delayed application? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9475#issuecomment-1774279834 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 October 2023 01:21:06 UTC