W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2020

Re: [csswg-drafts] [css-ui] Should interoperability be a goal for the `accent-color` spec? (#5480)

From: Brad Kemper via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Oct 2020 21:07:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-705194441-1602104857-sysbot+gh@w3.org>
> we will not utilize this property until a time that we can have a guaranteed utilization across UAs. 

If we are trying to normalize how and where UAs apply color, then I would say that goes way beyond what I would expect from a property called `accent-color`. Sounds more like it should be called `normalize-form-colors`. 

In my view, we should recognize that most/all UAs use a very limited color palette of colors that are not black or white (or shades/tints of the main colors), and that _those_ are the colors we want to change for theming. To go beyond that to insist of where colors go in the native control seems like something else altogether. For that level of control, there should be part selectors. But for changing the main blue of a UA's control to a corporate red, that should be a simple thing that you should be able to do with `accent-color` (or `accent-colors`) without worrying that it will otherwise change the overall design of the native control. 



-- 
GitHub Notification of comment by bradkemper
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-705194441 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 October 2020 21:07:40 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:20 UTC