- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Aug 2020 23:32:58 +0000
- To: public-css-archive@w3.org
The goal should be only and exactly enough specification to ensure that authors can use the property without browser-specific hacks, such that if an author makes it look good on one browser, they won't make it unreadable on another. Anything more is overly restrictive, anything less means the feature is useless. ---- > For example, is it ok for some implementations to use the accent-color to paint the background of a glyph, and other implementations to use it instead for the foreground glyph image? Or should we attempt to use accent-color in the same general way, across implementations, where possible? I think it's fine to use the color in slightly different ways, so long as care is taken by the UA to ensure that the control remains usable. For example, if they use the accent color for a background color, upon which they paint some sort of control-specific glyph (a clock, a calendar, etc), then they should *not* paint that glyph in the element's 'color', because there's no general requirement on the author that they ensure that color pair is contrasting (unlike 'color' and 'background-color', for instance). (Or the UA could be smart and pair the colors *if* there's sufficient contrast, and otherwise use black/white as appropriate, etc). For checkboxes the situation's more complex, since their entire body is just the one small bit of background with a glyph. Chrome recently switching to making it white-on-color instead of black-on-white like it's traditionally been has certainly made this more... interesting. I'm not sure what to do there. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-682242811 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 August 2020 23:32:59 UTC