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.