SVG 1.1 became a W3C recommendation on January 13, 2003. Seven years later, this page records my results of running various SVG implementations (web browsers and browser plugins) through the official SVG Test Suite. Last updated 2010-08-30.
The following picture indicates the results of running all 280 tests in many popular SVG implementations in the wild. Each test takes up a two-pixel strip in each column. I use a top secret scoring system ... ok, well actually I just use GREEN for "Pass" (2 points), YELLOW for "Almost Pass" (1 point), RED for "Fail" (0 points) and BLACK for "Fail with Crash" (-1 point). The "Almost Pass" scoring is subjective, so think of it as me giving out points for trying.
Now I know that I'm going to get complaints that the SVG test suite doesn't cover all functionality (I agree with you), nor does the score give a fair indication of other factors like performance (again, I agree with you), so please take this page as what it is: A data point from a guy who had too much time on his hands but is interested in seeing how the overall quality of SVG implementations improves in the future.
Some Final Notes
- The latest pre-release of SVG Web (Owlephant) scores only a few percentage points lower than IE9's latest preview
- Looks like Firefox 4 might break 80% by the time of its release.
- Chrome 6 Beta is the second browser to break the 90% barrier and get an A+ thanks to some more SVG Filter tests passing.
- Opera 10.61 fixed a couple bugs, nudging it over 95% (A++).
- IE9 looks like it's in good shape for a release.
- I did not add Chrome Frame plugin to this chart as it does not handle the SVG MIME type by default yet (see this bug). However, since it uses Webkit as its base, with the proper meta tag, it can function quite well in a pinch. You can get a feel for its level of SVG support by looking at the latest Chrome score above.
If you have something to say about this chart, please leave me a comment on my blog.