- From: Nishant J. via GitHub <noreply@w3.org>
- Date: Tue, 17 Feb 2026 23:11:29 +0000
- To: public-css-archive@w3.org
Absolutely, so my understanding with browser extensions is as follows (maybe this is bit of a reach) BUT Spec explicitly notes that forced-colors, system colors, and getComputedStyle() expose user preferences and can increase fingerprinting surface. BUT the spec says this for only user prefs; you can extend it to non-author interventions For example: Dark Reader (and similar OSS extensions) watches OS/theme state and then applies a consistent, cross-site restyling. Because that restyling often touches color-scheme / system colors / forced-colors-related behavior, any site (including 3rd-party iframes) can often detect “an extension is intervening” by observing computed styles and palette outcomes. https://github.com/darkreader/darkreader/blob/0706f4b800c12891d133f291aea36d696f4c9187/src/inject/color-scheme-watcher.ts#L42-L44 The referenced file does not inject styles itself; it detects system theme changes and notifies the extension, which then performs the styling elsewhere, but you get the point. -- GitHub Notification of comment by realArcherL Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13460#issuecomment-3917552853 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 February 2026 23:11:30 UTC