The data included in that table is totally wrong. Chrome supports most of the filter primitives defined in SVG spec, IE9 supports none of them, Firefox supports

The data included in that table is totally wrong. Chrome supports most of the filter primitives defined in SVG spec, IE9 supports none of them, Firefox supports vast majority but with serious performance issues. The real blocker for SVG is the lack of good authoring tools. Illustrator (used by the author of this article) apparently generates SVG files by rasterising many vector effects. I suspect that there is a bug in WebKit that breaks bitmap rendering in certain circumstances, this would explain why some Illustrator-generated effects failed on Chrome.