Skip to content

Commit

Permalink
[css-media-5] fixes #9475 - prefers reduced data tag question
Browse files Browse the repository at this point in the history
  • Loading branch information
argyleink committed Jan 17, 2024
1 parent b2d754a commit 4a267c8
Showing 1 changed file with 17 additions and 11 deletions.
28 changes: 17 additions & 11 deletions mediaqueries-5/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -3085,11 +3085,6 @@ Detecting the desire for light or dark color schemes: the 'prefers-color-scheme'
<h3 id="prefers-reduced-data">
Detecting the desire for reduced data usage when loading a page: the 'prefers-reduced-data' feature</h3>

Issue(4832): This feature may be an undesired source of fingerprinting,

This comment has been minimized.

Copy link
@argyleink

argyleink Jan 17, 2024

Author Contributor

this issue was resolved and the requested spec additions were made. this is a left over todo that was cleaned up.

with a bias towards low income with limited data.
A Privacy and Security section should be added to this spec,
and it should address this concern.

<pre class='descdef mq'>
Name: prefers-reduced-data
Value: no-preference | reduce
Expand All @@ -3116,12 +3111,23 @@ Detecting the desire for reduced data usage when loading a page: the 'prefers-re

The method by which the user expresses their preference can vary.
It might be a system-wide setting exposed by the Operating System,
or a setting controlled by the user agent.

Note: User agents may consider setting this based on the same user
or system preference as they use to set the
<a href="https://wicg.github.io/savedata/">Save-Data</a> HTTP request
header.
or a setting controlled by the user agent. User agents may consider
setting this based on the same user or system preference as they use to
set the <a href="https://wicg.github.io/savedata/">Save-Data</a>
HTTP request header.

Note: User agents should use their own user centered discretion when
handling a toggle of this value, whether it's toggled post page load
or during page load. A primary goal could be to not download unnecessary
data. Consider, if a page is already loaded with high quality assets and
the user changes their preference to reduced, the page should perhaps
not update the document right away, instead wait for an explicit page
reload invocation from the user. Consider also, if a page is taking a
long time to download and a user changes their preference to reduced,
this could be a nice point to save the user's bandwidth and immediately
switch to downloading smaller assets. User agents should be free to
implement logic as they see appropriate for situations like these, and
also be aware the situations exist.

<div class="example">
For example, a site could honour the preference of a user who
Expand Down

0 comments on commit 4a267c8

Please sign in to comment.