Re: [csswg-drafts] Allow specifying the "accent color" of a form control element (#5187)

So in the CSSWG [meeting](https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-676546952) today, I heard several things:
 1. There is a desire to see more examples of current implementations of each form control, across browsers and platforms. This will help people see what the variety looks like today, and gauge how well (or poorly) the [proposal](https://github.com/mfreed7/accent-color/blob/master/proposal.md) will apply to those controls.
 2. There is a concern that this new property would provide too much "power". They would prefer that the UA should take perhaps only a single accent color, and should decide how (or whether) to use that color. More like "try to use purple if you can", rather than "use purple for the checkbox background, and white for the glyph".

On the first point, I'm happy to do that work. I will likely expand the proposal with a discussion/background section containing a few selected controls' appearance on multiple browsers and platforms. My short list includes: checkbox, radio, select, and date.

On the second point, I do understand where the concern comes from, but I disagree. We've already [heard](https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-675141914) from developers on this thread that they have specific styling needs which would **require** some level of consistency among browsers. In the [example](https://timewarp.atjn.dk/) given there, the desire is to specifically control the "clock" glyph on a time control, and to make the rest of the control background one solid color. If this spec were "loose", then some UAs might decide to use `accent-color` to change the glyph color, and others might change the background behind the glyph. There would be no predictability, and developers would once again be forced to "roll their own" implementation. Or worse, they'll try to browser-sniff so that they can invert the colors to keep the appearance constant. For this to really provide value, I believe there needs to be some level of predictability.

Let me take a crack at expanding the examples, and see if that leads to any different conclusions. This might take me some time, but I'll check back here when it's complete.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 August 2020 21:55:16 UTC