- From: Alison Maher via GitHub <noreply@w3.org>
- Date: Thu, 04 Sep 2025 01:03:33 +0000
- To: public-css-archive@w3.org
I think it makes sense for `AccentColor` and `accent-color: auto` to produce the same results across the board to provide consistency for authors. This was something that @emilio brought up in https://groups.google.com/a/chromium.org/g/blink-dev/c/uP9MI1IdZj8/m/rJA77EppAAAJ, as well. > As long as they resolve to the same color at any given time, I think it's ok to expose one of them on a broader set of websites than the other @LeaVerou could you clarify what you mean by this point? As I understand it, if we limit the exposure of `AccentColor` to installed apps to mitigate the fingerprinting risk, we'd need to limit `accent-color: auto` in the same way in order to guarantee these use the same color in all cases, unless I misunderstand. Or are you saying that if only `accent-color: auto` is used on a page (and that page doesn't apply `AccentColor` anywhere), then we could expose it more fully? And if both are used, apply restrict both? If so, that also could potentially lead to author confusion in some cases. > ideally both should be available everywhere... Fwiw we did consider having system color keywords resolve to themselves, which would have allowed us to expose `AccentColor` in all the same cases we do for `accent-color: auto` today https://github.com/w3c/csswg-drafts/issues/5710. However, from what I recall, we decided against this as a result of the following issue on interpolation support for system colors: https://github.com/w3c/csswg-drafts/issues/5780 (if we want to reconsider any of these resolutions, that would be another the way to avoid the fingerprinting risk for `AccentColor`). Adding back to the agenda to discuss the results of the privacy review and whether the same restriction should apply to `accent-color: auto` as is being considered for `AccentColor`. -- GitHub Notification of comment by alisonmaher Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10372#issuecomment-3251286741 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 September 2025 01:03:34 UTC