I can also confirm that replacing the funky y aka ? in begin="?" with a y fixes the issue. In fact, Mac OS X still doesn't display one element from that .svg file, but that's probably due to gradients or fuzziness. At least now Chrome and FireFox display it properly, which they did not before.
I can also confirm that replacing the funky y aka ? in begin="?" with a y fixes the issue. In fact, Mac OS X still doesn't display one element from that .svg file, but that's probably due to gradients or fuzziness. At least now Chrome and FireFox display it properly, which they did not before.
I've now committed the fix to that pull request but the original bad .svg created by Inkscape is here : /github. com/burdges/ pond/commit/ 18cdb4e86666ec7 c22eba2c5068ed4 8dc2ec4b4f
https:/