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: Sat, 03 Oct 2020 06:44:11 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-703056656-1601707449-sysbot+gh@w3.org>
>So in Chrome's case, an unchecked checkbox would just use the 'background-color' (and perhaps 'color' for the border?), while a checked checkbox would use the 'accent-color' for the bg and the 'background-color' for the check. If it determines that those two colors, as provided by the author, don't contrast sufficiently, it can fallback to a second 'accent-color' specified, or adjust the specified accent-color lighter/darker, or ignore it and use the default, as desired by the UA.

I would not expect `color` to affect anything but text, and not necessarily text that was several layers deep, like the text in a button in a file upload control. And it would affect borders that were set to currentColor, which wouldn't necessarily be the same across UAs (they wouldn't have been in Aqua). And I wouldn't expect all UAs to use a text glyph for the checkmark or other icons. An image (SVG? Or even a PNG) would be reasonable and also not necessarily currentColor. 

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 3 October 2020 06:44:12 UTC

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