- From: Jeffrey Yasskin via GitHub <noreply@w3.org>
- Date: Wed, 25 Feb 2026 23:58:45 +0000
- To: public-css-archive@w3.org
jyasskin has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color] Privacy considerations should describe how system colors are chosen in practice == https://drafts.csswg.org/css-color-4/#privacy currently consists entirely of > This specification defines "system" colors, which theoretically can expose details of the user’s OS settings, which is a fingerprinting risk. The likely amount of fingerprinting depends on the distribution of users' choices of system colors. If operating systems encourage users to [pick from one of 8 palettes](https://developer.apple.com/design/human-interface-guidelines/color#App-accent-colors), there's much less risk than if [the operating system infers an accent color from the user's personal background image](https://developer.android.com/develop/ui/views/theming/dynamic-colors#how-system-creates). There's debate about whether even 3 bits is too many, or whether fingerprinting is a lost cause, and so we should be willing to expose a color that's unique to a single user. To help the various positions in that debate decide what to ship and under what restrictions (e.g. only installed apps?), it would be good for the spec to describe what we know about the actual distribution of system colors. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13561 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 February 2026 23:58:46 UTC