- From: Lea Verou via GitHub <noreply@w3.org>
- Date: Sat, 30 Aug 2025 10:06:08 +0000
- To: public-css-archive@w3.org
> Right, but LeaVerou and alisonmaher's points were that having inconsistent exposure on `accent-color: auto` and AccentColor is confusing. Because they have different levels of fingerprinting, they aren't held to the same level of scoping. If one is fully available everywhere, but the other is only scoped to installed websites, it introduces an inconsistency that developers might not be expecting. Because of this, I think it makes sense here to scope to the level required by the riskier of the two. I can't speak for @alisonmaher, but the inconsistency I was talking about is that we should absolutely avoid them resolving to different colors **on the same page, at the same time**, e.g. `AccentColor` resolving to blue so web components using it are blue and native form controls use `accent-color` which resolves to pink. 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, though ideally both should be available everywhere... -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10372#issuecomment-3239164668 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 30 August 2025 10:06:12 UTC