- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Oct 2020 23:20:56 +0000
- To: public-css-archive@w3.org
> Right! This is why I created this issue and have been lobbying for other implementers to say what I'm about to say: if an author says accent-color: black white then they should get the same color background in all browsers. A.k.a. option A. Okay, that's not what the current proposal says. ^_^ Fixing that would help, since you've continually been *referring to* the current proposal. > I suspect others on this thread will vote for option B. I would not take that as an assumption. There's been a lot of confusion around this issue, and *nobody* wants a specification that will end up being worthless to authors due to giving totally different results across browsers. What you're instead seeing is (a) some degree of reluctance to commit to *the current spec* as the proposal (which is what you've *explicitly said* "Option A" is during the call!), and (b) some degree of reluctance to define form styling *at all*, and flailing for "Option B" as a "well, I guess Chrome can do whatever, we'll continue to do nothing so it doesn't matter" fatalist choice. ----- Going back thru the minutes, see for example: > masonfreed: Looking for a direction, interop vs hint. Interop is full proposal as presented. B is a striped down version with no normative text or guidance on how to do accent-color. A or B with a link in the thread. This is where you've been saying "Option A" is "what's currently in the proposal", *not* the more generic thrust you're talking about now. If you don't remember tying "Option A" so explicitly to the exact current text, that's part of the confusion. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-702997513 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 October 2020 23:20:59 UTC