Re: [csswg-drafts] [media-queries-5] should "prefers-reduced-data" be binary or not (#4833)

The CSS Working Group just discussed `prefers-reduced-data`, and agreed to the following:

* `RESOLVED: prefers-reduced-data remains binary`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: prefers-reduced-data<br>
&lt;fantasai> github:<br>
&lt;fantasai> argyle: This is about preference for reducing data<br>
&lt;fantasai> argyle: Can be expressed in headers<br>
&lt;fantasai> argyle: and this feature exposes as MQ<br>
&lt;fantasai> argyle: ..<br>
&lt;fantasai> argyle: can see what Chrome plans to reduce<br>
&lt;fantasai> argyle: Goal is to send less bits over the wire to users that have that set<br>
&lt;fantasai> florian: Currently it's a binary preference<br>
&lt;fantasai> florian: Earlier we wondered if it needs to have multiple leves<br>
&lt;fantasai> florian: State today, the JS API being proposed along with this, there are only two levels<br>
&lt;fantasai> florian: So should only have two levels for now<br>
&lt;smfr> q+<br>
&lt;fantasai> florian: This feature can be used as boolean, so if we want to add more values later can<br>
&lt;fantasai> florian: but current proposal is to close as no change, leave as a binary<br>
&lt;fantasai> argyle: OSes don't have degrees, just binary switch<br>
&lt;fantasai> argyle: can expand later if needed<br>
&lt;fantasai> smfr: More levels is more fingerprinting surface<br>
&lt;fantasai> smfr: Apple already have concerns about this<br>
&lt;fantasai> smfr: allows targetting ppl on low-bandwidth, which is often poorer community<br>
&lt;fantasai> smfr: e.g.<br>
&lt;fantasai> florian: There is a privacy fingerprinting warning issue in the spec about this, and it is visible in the spec<br>
&lt;fantasai> astearns: So consensus seems to be keep binary for now<br>
&lt;fantasai> RESOLVED: prefers-reduced-data remains binary<br>
&lt;chris> q+ after florian<br>
&lt;chris> sigh<br>
&lt;astearns> ack after<br>
&lt;astearns> ack smfr<br>
&lt;chris> q+<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 30 July 2020 17:06:21 UTC