- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2024 19:00:38 +0000
- To: public-css-archive@w3.org
To summarize @frivoal’s concern: WebKit lies about `accentColor` but still uses the correct OS accent color in form controls. You can see this in action in this demo (set your OS default color to something else first): https://result.dabblet.com/gist/d9354b57012bc1f9eaf8edfbc2b39bed/30d00e3ac6eae4dab6e6ac5a05419c62975f5fd3 However: 1. This is a problem with the *existing* `accentColor` keyword, and if anything is *reduced* by this change. 2. Even if the OS default were useless, authors having a universal "contract" to communicate accent color to components is still very valuable. 3. I’d argue this is a bug in WebKit and it should instead use the correct color and not expose it if they are so concerned about fingerprinting. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5900#issuecomment-2377715054 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 September 2024 19:00:39 UTC