- From: James Atherton via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Aug 2020 05:16:31 +0000
- To: public-css-archive@w3.org
If the use counter comes back small, then there's no reason to delay further. If the use counter comes back large, it's going to be almost entirely false positives from the previous 4 years of development, which are now likely broken. Then, still, there's no reason to delay further. ---- I suggested paths in the chromium issue to mitigate false positives from the past but they were not implemented. Further, my launch this month will contribute over 300 false positives per page load in Chrome 86+ since I am deliberately triggering this behavior as an example of what to avoid and how to use the reset layer to fix it. The cumulative false positives from this project could easily be in the millions. This was also dismissed as "unlikely to make a real difference in the result" and no steps were taken to mitigate them either, despite offering multiple ways to do so. https://bugs.chromium.org/p/chromium/issues/detail?id=1110188 ---- **This use counter is not helpful in determining compatibility** and only serves to delay (and temporarily double down on) @andruud's _initially_ well-intentioned decision that, without running a use counter, disrupted 4 years of advanced CSS development and experimentation without an inexpensive alternative path  Doubling down on a negative-outcome decision, even in the face of consensus moving in the opposite direction, is not a good look - it looks spiteful. -- GitHub Notification of comment by James0x57 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5370#issuecomment-674351113 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 August 2020 05:16:33 UTC