- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Apr 2021 08:06:20 +0000
- To: public-css-archive@w3.org
I guess it can't be an env variable: such variables are evaluated independently of where you are in the tree, and thus would always return the UA's default accent color, which we cannot share for fingerprinting reasons (see in https://github.com/w3c/csswg-drafts/issues/6158). If we want the local accent-color, as set by the author, we need something context sensitive, so that wouldn't be an env variable, but something more like the `currentColor` keyword. That said, I wonder if this is really worth the cost, as there's an easy work-around. If an author needs this, they can just as well set their own `--accent-color` custom property, and use its value to set both the actual `accent-color` property and whatever other place they wanted to use that color in. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5900#issuecomment-826608664 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 April 2021 08:06:22 UTC