- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Sep 2020 18:22:46 +0000
- To: public-css-archive@w3.org
> Please disregard questions about how the details of each of the above options are to be specified. Those are great questions. But we first need to decide the basic structure of this feature, by deciding on A or B. No, we can't. The question you're trying to ask already has an answer: the property needs to be specified well enough that authors can get reasonable results across browsers (however that happens) and no farther; overspecifying is a no-go because there's too much variation already (and always will be), while underspecifying makes the entire property worthless. So this isn't actually a question needing to be addressed, and answering it anyway doesn't help you advance this spec in any meaningful fashion. The question needing to be answered is precisely what the colors in 'accent-color' are/do. I've given a proposal that I think actually works. The current proposed spec *does not work*; it will give results - such as `accent-color: black white` giving a checkbox with a white background in some browsers and a black background in others - which make the property effectively useless for authors to actually match the controls to their page in a way that reads properly. So your (A) is bad, but (B) is also bad. Neither result gives us a spec that can actually be implemented and produce a feature that's useful cross-browser. Let's discuss how to achieve that goal, rather than trying to wordsmith or reach a false consensus. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-701561947 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 September 2020 18:22:48 UTC