- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Oct 2020 19:25:43 +0000
- To: public-css-archive@w3.org
I've just [closed](https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-709542140) the "interoperability" issue that I opened, as it didn't help move the conversation forward as I had hoped. It actually seems to have somewhat derailed it, and that's likely my fault. The big conclusion I took from that discussion was that [my proposal](https://github.com/mfreed7/accent-color/blob/master/proposal.md) bites off too much, and most people seem to agree that `accent-color` should be less about "full control" of colors, and (as @samuelbradshaw [nicely puts it](https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-704322971)) more about "dusting" the existing controls with a color. In other words, `accent-color` seems like a good fit for the "I want to change the theme and ensure contrast / readability, but don't necessarily need to control form UX so tightly", and **not** a good fit for "I want to make sure my form control looks exactly this way". Other technology is better for the latter. And in this context, interoperability can take the form of "achieves the intended purpose reliably across browsers" as opposed to "generates the same pixels across browsers". As such, I think we should consider other proposals for the `accent-color` feature. In particular, @fantasai has made several such proposals (e.g. [1](https://github.com/w3c/csswg-drafts/issues/5544) and [2](https://github.com/fantasai/accent-color/blob/master/proposal.md)), and we should consider those and any others. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-709542240 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 October 2020 19:25:46 UTC