- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 07:10:11 +0000
- To: public-css-archive@w3.org
> Are there any use cases where authors need to access the OS default accent color even if there is an accent-color set? I don't see any, but I could well be missing them. But if there aren't, I don't understand the rationale for this — it complicates the language and the number of keywords authors need to learn with no discernible benefit. Remember theoretical purity is at the bottom of the PoC. An additional point: even if there are such use cases, they will be possible by capturing the corresponding colors on the `:root` with registered custom properties, and accessing them later regardless of if they were overridden. It could be even possible to store both the light & dark versions of them via setting two different `color-scheme` values on `html` and `body`, and storing two sets of custom properties there. So, I'm for the `accent-color` following the overridden value, as this will cover the more common use cases and will remove the current confusing behavior, and more complex cases will still be possible, even if a bit hacky. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5900#issuecomment-2306440750 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 07:10:12 UTC