You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bikeshed currently adds an automatic test widget to CSSWG specs, both on drafts.csswg.org and on W3C /TR. This used to be very helpful, giving an implementation report broken out by spec section.
The reports rely on manual test running by an actual person, which I previously saw as a good use of my time and now don't because running a known-incorrect test has no value
The tests and the reports give an inaccurate and very negative view of the state of implementation
There is no prospect of the Shepherd test situation improving (the recent "month of work" to stop the drafts server falling over all the time did not include any work on the test area)
The presence of the widget encourages people to run tests, and they will then draw inaccurate conclusions or even change implementations "to pass" known incorrect tests.
Then adding this link to all CSSWG specs has negative value and I am asking that Bikeshed remove (comment out code that adds) this widget. If at some future time it starts working again it can always be added back.
6237 well maintained tests? Or 118 out of date ones?
Bikeshed currently adds an automatic test widget to CSSWG specs, both on drafts.csswg.org and on W3C /TR. This used to be very helpful, giving an implementation report broken out by spec section.
Given that:
Then adding this link to all CSSWG specs has negative value and I am asking that Bikeshed remove (comment out code that adds) this widget. If at some future time it starts working again it can always be added back.
6237 well maintained tests? Or 118 out of date ones?
Related:
The text was updated successfully, but these errors were encountered: