- From: Jen Simmons via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Oct 2020 01:56:23 +0000
- To: public-css-archive@w3.org
Honestly, I am still very confused about this discussion. It still sounds to me like the explicit debate is: >A: Should we try our best to articulate how this could work, knowing implementations won't be identical? >or >B: Knowing implementations won't be identical, should we try our best to articulate how this could work? Well, not really. While the resulting consequences of this decision are laid out as: >A: Specify exactly the one way this must be implemented, so we have interoperability. >or >B: Write up almost nothing, delete most of what's been proposed. I believe that it would be best to articulate, in writing, how an `accent-color` property could work, with lots and lots of detail, form control by form control, with multiple options. To articulate how it _may_ work. With the shared hope that implementations are as interoperable as possible. With an understanding that interoperable has never meant identical. I believe we need flexibility in the text that recognizes the complexity of this space, and can provide a clear guided path for a variety of implementations. Such an approach will add to interoperability in this case, not prevent it. I honestly cannot tell if that means I vote choice A or B. Obviously, interoperability is our goal. Interoperability is a fundamental principle of the work of the CSSWG. That's not at question. The question is what path is the best way for us to get the maximum interoperability possible — in a way that's most useful to Authors, given how complicated the evolution of browser controls has been in the past & presumably will be in the future. Simply defining one way browsers should implement `accent-color` for each control, without providing any guidance for what to implement when things “aren't that simple” is not a path to the maximum interoperability. -- GitHub Notification of comment by jensimmons Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-706637482 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 11 October 2020 01:56:25 UTC