I published my results of running ten different SVG implementations through the SVG Test Suite.
I ran the tests on various flavours of Firefox, Opera, Konqueror, Safari, Adobe SVG Viewer, Renesis, and Batik. Go check out how your favourite web browser or SVG plugin scored when I ran it through all 280 tests: Click Here.
This is one of those times when I almost hesitate to even publish this because people will officially know I wasted hours of my life browsing web pages to obtain these results. Then again, we all waste hours of our lives browsing web pages - the only difference is we don't record our findings in a spreadsheet.
I hope some people will find this interesting. Some people might consider it a challenge. Other people may find it discouraging, disappointing, a waste of time, an over-simplification, or even offensive. Oh well, at least now I have my own scoring system for anybody who wants to put out a SVG plugin or support for SVG (Microsoft, care to give it a whirl?).
I have a mac and I’d like to see how complete WebKit is when it comes to SVG.
Thanks for your help, Mike – I have updated the page with your results.
Very nice indeed. This is a great comparision to see, side by side. I presume the large red chuck in the middle of a lot of them is declerative animation? Is there any way a cunning Javascript rollover could be added to say what test a line represents?
Nice one!
Allan
> I presume the large red chuck in the middle of a lot of them is declerative animation?
Yes, you are correct.
> Is there any way a cunning Javascript rollover could be added to say what test a line represents?
I had similar ideas. I could also turn this into a SVG document that has 280 * 11 rectangles, each wrapped in a svg:a element. This would make the process much more complicated than just copying a region in an Excel workbook and pasting it into Microsoft Paint. Oh well, something to work on later.
The test misses TinyLine (www.tinyline.com) and BitFlash (www.bitflash.com) SVG players. Even BitFlash is currently moving to Mobile market, they still have the PC version available.
I didn’t find my SVG animations working besides Opera 9 and Adobe plugin, when I removed some unesserary META’s and still waiting somebody to provide me a proper SVG drivers. My animated stories are around 2 minutes length and are SVG Tiny 1.1 compatible. I wrote an article Experiences producing SVG animated movies to my blog about it.
It’s worth noting that nightly builds of WebKit have some of the more bleeding-edge SVG features disabled. I believe filters and animation are two features that are implemented and working correctly inside Webkit but are disabled by default until more testing can be done.
Thanks, Mark. Yes, I’m aware that filters and animation have been disabled in the Webkit nightlies. I also heard that Maciej was going to disable the <use> code, but that decision was later changed (which is a good thing!)
It would be nice if you implemented the graph as an SVG which named the test as you hovered the mouse. That way I could zoom in and see which ones failed. It would also help if you grouped the rows by module.
Nicholas – you read my mind! This is actually very close to what I was thinking (minus the grouping by module). I’m not sure I have the time for this at the moment though, it’s a lot of tests to run and that took up the bulk of the time.
Your spreadsheet would be very much more interesting than the image; if you don’t have the time to fix that, could you perhaps at least publish it, or even upload it to editgrid, so that others could do the work you don’t have time for? Like making an Exhibit of it, for instance, to add facet browsing (on module, browser, and probably other aspects too). CSV file?
I love the chart; however, is there any chance of seeing CSV (Corel SVG Viewer) results?
Wow – someone actually asked for CSV! 🙂 Is there a place I can download the last supported version of CSV without having to sign up for an account with Corel, etc?
Jeff, your chart is one of the most informing pieces of information I have seen on SVG support so far. Great work. I think it’s so great that it should get a permanent domain of it’s own. You could have a whole website evolve around it. Please keep it up to date
Cheers,
Jacobus
P.s.1. Good luck fining CSV. I’ve tried without luck.
P.s.2. Of the mark: I’ve spent 2 days trying to get matrix.inverse() to work on “inline SVG” in Safari beta. If you come accross a hack…. please share it. I desparately need it.
It’s disappointing that Corel requires you to register to download free software… I imagine that stops a great deal of potential users right there. There is bugmenot though..
I’m surprised that CSV isn’t on download.com or any other download site. I didn’t see anything in the license or terms of service that would prohibit that, but perhaps I missed it.
Stephen, My understanding is that CSV isn’t as good as ASV – and ASV is freely available for download and what the majority of IE users would have – that’s the reason I left CSV off. I may one day get around to it, but if I remember correctly it hasn’t been supported for even longer than ASV …
nitpicking:
– rotate 90 degrees, so it’s easier to read the names of the viewers. As background of these names take the same GreenYellowRed, but now all ordered GreenYellowRed (for easy comparing between viewers)
– make date it’s own column
– You forgot the B from Beta with Batik 1.7
– Many people wouldn’t call Batik a plug-in (i’d like a plug-in version of Batik actually)
I did a similar thing for Inkscape http://wiki.inkscape.org/wiki/index.php/SVG_Test_Suite_Compliance
however somehow the copy of the SVG test suite only has 275 tests? might be an old one on my pc (oh well). As you say the “almost pass” is very subjective, so I tried to be as strict as possible 😉 oh, and by your scoring Inkscape gets about a 53% which doesn’t seem a lot for a SVG editor… still at least some parts are improving (filters and parts of the text tests) and most of the features it supports it can edit 🙂
tomh
@stelt: Can you clarify what you mean in the second sentence of your first point?
@tomh: Interesting information – so Inkscape, Mozilla and Webkit all render roughly the same subset of SVG?
I suppose you could call the subset that Inkscape / Mozilla / Webkit implement the easy to do or the needed to render the most common SVG’s subset.
For example the SVG fonts issue means that you have to start doing the job that you would normally expect the OS or a low level library to provide, so you ever design it strait form the start or you say, I’m going to let the OS deal with this for the moment and make this useful for 99% of cases and worry about the (very) few times you need SVG font support much latter. (which is kind of self perpetuating)
The same goes for animation, its much easier to market Inkscape as a Vector graphics editor which only does still images than it would be to have it support animation and not be easy to use or lacking basic editing capabilities…
Hi there,
Have you considered running the SVG tests on the Amaya browser? I’ve found it to be slightly below Opera, but above most of the others – it supports animation, etc…
Cheers.
Richard,
Thanks for the idea – I wasn’t aware that Amaya was very strong in its SVG support – I’ll have to check it out eventually.
Jeff
@stelt: Can you clarify what you mean in the second sentence of your first point?
clarifying “nitpicking:
– rotate 90 degrees, so it’s easier to read the names of the viewers. As background of these names take the same GreenYellowRed, but now all ordered GreenYellowRed (for easy comparing between viewers)”:
Now the backgroundcolor of the names is one of 2 fixed colors depending on whether it’s a plug-in or native SVG rendering. Now say the test result for a viewer is GYRGYRGYRGGY (Green,Yellow,Red), then the backgroundcolors for the name of the viewer would be GGGGGYYYYRRR (to easier compare the percentages)
Thanks for so quickly adding all the cutting-edge viewers in your comparison now Opera has released their 9.5 Alpha1. In your image you forget “b1” (beta1) behind “Batik”. Pretty soon the first Beta of Firefox is coming out. I’ll be checking your comparison right after 🙂
BTW, Firefox 1.5 is no longer supported, though still used by about a quarter of the Firefox users.
Stelt,
Thanks – I know that I have to implement a couple of your suggestions still too. I’ll get to that eventually 😉
Jeff
End of the month we’ ll have Safari 3, so native SVG support has then spread to all (1%+) modern browsers (read all browsers other than Internet Explorer). At the same time Opera, already in the lead will release 9.5 beta. And of course we’re also all looking forward to Firefox 3 beta.
Thanks for the svg-support image.
This chart is a really useful consolidation of lots of info. But based on what I see, it appears that Firefox 1.5 and 2.0 have approximateley the same level of SVG support. I have been struggling with making my SVG charts appear without using the Adobe plugin, so I thought that 1.5 would solve all my problems. Alas, no such luck. Any suggestion as to where to look or whom to ask for assistance getting SVG to appear correctly? SVG seems to be losing marketshare to Flash, and I worry that I am going down a road that will no longer exist in a few years.
Thanks,
Michael
@Michael B: Yes, there was very little work done from an SVG perspective between Firefox 1.5 and 2.0. I would suggest you check out Firefox 3.0 which has a good amount of improvement. Of course, the “reference” implementation should be Opera 9, but it’s hard to justify coding for that browser with only ~1% market share. Please check out the Yahoo! Groups svg-developers and ask your questions there. The SVG wiki is a good place too. In terms of “marketshare”, SVG never had any to begin with, so it’s hard to say it’s “losing” marketshare against Flash.
Just a quick question about the updated graph: Why does “Firefox 3 Beta 2” have a lower percentage than “Firefox 3.0 preA8” on your chart? Just curious if its a typo or if Mozilla removed SVG functionality between Alpha 8 and Beta 2.
@kwerboom: Beta 2 had a couple small regressions from pre-Alpha 8. Robert Longson has already contacted me about this updated chart and I have sent him the .xls file with my notes. This isn’t removed functionality so much as some (hopefully) minor bugs.
I notice you’ve added Internet Explorer to your list. Do you know something we don’t?! 🙂
@Gyrobo: No, I’m just trying to increase awareness that IE is the only browser out there that doesn’t support SVG yet.
Gotcha.
Any tests for librsvg? I ask because I’m writing up SVG renderers for the MediaWiki manual: http://www.mediawiki.org/wiki/Manual:Image_Administration#SVG
@David: Sorry I haven’t experimented down to the library level (only at the desktop browser level, really). Things get really murky for me when trying to investigate library dependencies. This page says that Mozilla can use it. This page hints that there’s some relationship between cairo and librsvg. I know that Firefox 3 uses cairo as its graphic rendering layer…
you typed year 1905 for asv3 in your table
AG: I believe it’s a joke. I personally found it hilarious! 😀 Also, nice move on the IE7: 0% sarcasm… 😉
Thank you for this great piece of work and for the many hours (I can only imagine) you invested on it! 🙂
@Helder: Actually, the ASV date was an accident – but in retrospect, a pretty funny joke that I’ll now take credit for. 🙂
Can you maybe take a look at http://wiki.svg.org/Viewer_Matrix to see what needs updating there, as you know a lot of the matter
I’m interested to know what row correspond to what test.
Could you provide the raw data results ?
Thanks !
Hi Jeff,
why the the has the pre beta 4 th same result in percentage as the pre-beta 3? (by the way: the pictures seem to be right because the beta 4 has not so many bug/errors and “no’s”)
mfg
mabdul
@mabdul: There were several improvements in the latest Firefox 3. However, there were also several regressions due to Bug 418164, which apparently has now been fixed. It was just an odd coincidence that the scores happened to be the same…
Safari 3.1 is out, i’m looking forward to seeing it compared
@stelt: Thanks. I’ve played with Safari 3.1 through the Apple Developer Connection, but I couldn’t get a straight answer on whether I was allowed to record the results publicly or not. Furthermore, it confused me that Safari 3 was in Beta and never was officially released – now they’re on to Safari 3.1 but it doesn’t say Beta on the website. Anyway, I’m happier with Safari 3.1 as it picked up some of the fixes from WebKit that makes this site render properly. I’ll get to updating svg-support some time this week with the results.
Maybe you should be leading the implementors panel at SVG Open.
So, can we see a spreadsheet of the results (either in comma separated or excel or something else)?
@Aaron: Click on the image. I hope that works…
hi jeff,
i wrote down the same question like in the mail:
what about testing prince xml (www.princexmilö.com) they have already a good documentary since 5.1….)
mfg mabdul
Can you maybe add a link to http://wiki.svg.org/Viewer_Matrix near the tri-color image?
@stelt: Done.