Re: [csswg-drafts] Exposing Implementation Status

I'm strongly against this: we've seen vendor's marketing departments start to control their contributions to testsuites previously (releasing thousands of very shallow tests that are of very little value to increase their pass percentage, very selectively releasing tests they pass and competitors fail, etc.), and it's already true in many specs that colour coding based on pass percentage is relatively meaningless (some specs have the majority of their tests testing edge-cases and hence caniuse/mdn/etc. would probably be willing to consider a low percentage as support, whereas some have a fairly shallow testsuite where you'd want a higher percentage bar).

Given various people have proposed such things around this, I've finally got around to writing to try and give some proper place we can point to in future as to why we want to avoid anything that might lead to gamification of the testsuite.

GitHub Notification of comment by gsnedders
Please view or discuss this issue at using your GitHub account

Received on Thursday, 13 July 2017 16:47:30 UTC