CooL tests for browsers

Here are some CooL tests:
volume one - using createElementNS. http://srufaculty.sru.edu/david.dailey/svg/createElementBrowser.html

I'm calling them CooL since they are kind of cool, but I would not like to think they are in any way so definitive as those Ken Kesey might have proffered. Basically, they are examples I've made not to be browser tests, nor as tests of the spec, but rather because of a curiosity as to whether or not some particular effect could be accomplished.

A good many of them were created when only ASV+IE was around to run them, and I have been pleased to watch as other browsers have come along and are able to make them work. I think, that finally (with some recent advances by FF4), none of these particular tests is any longer in the category that only ASV+IE handles them "correctly" which makes me think that maybe they are correct.  or at least another browser developer and I stumbled into the same way of handling something.

Not surprisingly, given the way many of these tests were created, ASV passes all 19 of them. Though, please, ne t'en fais pas, as subsequent volumes emerge (if I get the energy): for script-less animation, or for filters, or for scripted things that don't insert or delete elements from DOM, there will be examples where other browsers shine and ASV barfs. I have been trying to get Windows 7 to run on one of my office machines, so that I might test IE9b (which is likely to be adversely affected by my fondness for SVG/SMIL) but the machine has thus far been coyly ignoring my overtures.

The point system employed shows ASV>O>FF4>C>S which might not surprise many folks. What surprised me was how high FF4 has gotten. There is also a "best of show" category and each of {ASV, O, FF4 and C} received two of these ribbons for outstanding performance above the other browsers. This is entirely subjective, whereas other things only mostly subjective.

Do let me know if you see a) bugs in my code that prevent a browser from doing it properly (and by this I don't mean things like "if you wouldn't use SMIL it would work") or b) if you find that a recent bug fix in browser X that has just made one of these things work.

These are quite different than the things the SVG IG is doing at http://code.google.com/p/svgtorture/ which I think are much more focused on particular SVG features than on omnibus aggregations. That work appears to be systematic and thorough while this is not. It does give some idea though, of how browsers fare amidst some fairly complex content. It also answers some FAQ that I've been getting about where can I find some interesting examples, and could I organize some of the information at http://srufaculty.sru.edu/david.dailey/svg/ so it might be easier to find things and to know where they might work.

They are also different from what Erik and Vincent have been doing at http://svg-wow.org/ (I see the Gandhi quotes demo is now up ! a must-see! ) since the criteria for inclusion there would seem to require a lot more work!  They also go to greater lengths to work through browser limitations than these examples. Their examples are also a lot more artful!

Cheers
David