- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Oct 2020 00:09:58 +0000
- To: public-css-archive@w3.org
> "But let's debate that later, after we decide that Option A is the right way to go." The problem you're running into on the call is that people are reluctant to say "Yes, let's go with something like this", because they're afraid that doing so will be seen as "yes, Chrome is okay to ship what the spec currently says". The details of the proposal matter; this is why we *haven't* succeeded at doing this precise thing for 20+ years. But again, "here's some colors, do *something* with them" is not actually an option on the table. That's not a spec, and I will formally object to attempting that; it's *giving up* on there being a spec, and I'd rather be more honest and continue not having a spec instead. The only actual options are: 1. Come up with a reasonably detailed, but not *too* detailed, specification for how UAs must use the colors, if they're using them at all. This must be defined such that an author can use the property to style elements on the page, and have a reasonable guarantee of them looking okay in all browsers regardless of any browser's particular styling conventions. 2. Continue to leave form styling an unsolved problem. Continue iterating on the spec and reaching consensus on the details; trying to push for an even more explicit "yes" on (1) feels like attempting to lock down a solution before there's consensus. > Thanks. Help would be appreciated in "fixing" this issue, as I've tried numerous times and apparently failed 100% of the time. Yeah, let's do that in another issue. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-703008649 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 00:09:59 UTC