-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preference Media Queries Privacy Concerns #515
Comments
An idea I mentioned in #507 and @bramus also raised in WebKit/standards-positions#145 was to make it so UAs could by default return a "no-preference" response for media queries where it's deemed the fingerprinting risk is too high vs the perceived benefits. Then allow the user to opt in to exposing their true preferences where the user can decide the privacy trade off is worth it. |
FYI MQ editors: @grorg @frivoal @tabatkins @dlibby- |
This should probably be done in the CSSWG rather than in interop. |
Closing to discuss further at w3c/csswg-drafts#3488 |
Description
Media Queries Level 5 introduces numerous media queries based on user preferences. While some ship cross browsers others don't and more have been proposed but not specced. This is due to perceived privacy risks, each preference query introduces new fingerprinting vectors that could be abused.
This investigation area would focus on coming up with a satisfactory solution to these privacy concerns while enabling these important accessibility features.
Rationale
I originally proposed #507 but I decided an investigation proposal for solving the privacy concerns was probably a better idea.
Currently
prefers-color-scheme
,prefers-contrast
andprefers-reduced-motion
are implemented cross browser. Along withforced-colors
.inverted-colors
exists in WebKit (see #506), andprefers-reduced-transparency
exists in Chromium.There's also proposals for new additions such as
prefers-reduced-strobing
,prefers-shapes
and others. Probably more that have yet to be proposed.Investigation Roadmap
w3c/csswg-drafts#3488 tracks the overall privacy considerations work for Media Queries Level 5.
The text was updated successfully, but these errors were encountered: