Re: pilot case?

You’re right, we should probably make tests cases and hand them over to the CSSWG. They would appreciate to have us contribute to their test suite and show the prollyfills not only enable the authors to use the technologies more quickly, but also let the implementers implement them more easily.


I guess your demo test page already contains a lot of test cases, now we should turn each of them into a separate test case (probably a reftest, this is the easiest option I think) and I can add them to the CSSWG mercurial (I already have an account on it).


I may even work on this tonight, this doesn’t seem relatively time-consuming, the most difficult part is to write the assert statements in plain English ^_^




De : Brian Kardell
Envoyé : ‎lundi‎ ‎6‎ ‎mai‎ ‎2013 ‎18‎:‎15
À : public-nextweb@w3.org


I worked this up over the weekend, it's just started but perhaps we
can use it as a pilot case: It is comparatively simple and already in
draft form with the CSS WG.

https://github.com/bkardell/selectors-L4-link-prollyfills


In other words, can we use this (or something else if the group
prefers) to figure out how to make a process work?  Not just in terms
of fork/evolve, etc - but in terms of making this a progressive
process... Ideally as these get better, we would add test cases or
examples that add value to the standards body (CSS WG in this case) so
that, assuming a version _becomes_ a standard - those things are
already contributed, agreed upon by a number of implementers, etc.

--
Brian Kardell :: @briankardell :: hitchjs.com