3 ms·
> all modern browsers have good support for SVG 1.1 That is simply not true, as I've explained above. You can't call an SVG 1.1 file poorly authored because S
by jahewson 14y ago
> all modern browsers have good support for SVG 1.1
That is simply not true, as I've explained above. You can't call an SVG 1.1 file poorly authored because Safari has a bug displaying it, or Firefox doesn't support the filter you used. The fault is with the browser, not the end user.
> It was present in SVG 1.1 for years and it's still not properly implemented by all browsers
Now you're just contradicting yourself! Though "good support" was an ambiguous weasel phrase in the first place.
It's clear that you don't know much about what browsers do and don't support and what bugs exist, because your previous answer was so naively wrong. You need to not just trust statements like "supports SVG 1.1" on Wikipedia and actually apply your mind to discovering the nuanced details of what's actually out there.
- jarek-foksa 14y agoI'm not contradicting myself, as I said: except for filters, animations and fonts, all modern browsers have good support for SVG 1.1. By "good support" I mean it's on pair or even better than HTML5 and CSS3 support. Files that break cross-origin policy or use non-standard tags are poorly authored by my standards. I have a lot of experience with SVG under WebKit-based browsers and so far everything renders just fine for me except for advanced features mentioned earlier.