Weird rendering in Gecko and Webkit, maybe can be fixed with Inkscape

edit

This image rendered incorrectly under Firefox 3.0 and Google Chrome. I would claim that this indicated a bug in the graphics library that produced it, but then again we know that sometimes multiple rendering engines in browsers CAN share the same bugs. The image doesn't seem to have been corrupted - it displays correctly in Opera. I expect that it would display correctly in Inkscape, and Inkscape might be able to save it in a way that makes it more compatible with the Webkit and Gecko implementations. I would recommend this course of action. I do not yet know enough about SVG to be able to say why it's not rendered correctly in some contexts. Anyway I'm placing it on my watchlist. Perhaps I can come back later with a patched version or something. As nobody reads image talkpages apparently, I guess this is largely a note to myself (that's cool) SneakyWho am i (talk) 16:13, 4 March 2009 (UTC)Reply

I can read this message, but I didn't create it. All I know is it renders well on Wikipedia. SockPuppetForTomruen (talk) 19:51, 4 March 2009 (UTC)Reply
Uh, I occasionally do, but hardly ever. Professor M. Fiendish, Esq. 13:06, 14 September 2009 (UTC)Reply
I can confirm the weird rendering and have a screenshot here. If I just right click and view the image, I get a .png that always renders as expected. But if I left click the image, I get the E8_graph.svg file that doesn't render properly. This is a brand spanking new release of SeaMonkey and very up-to-date OS. I get the same in Safari which isn't too surprising. Wurdeh (talk) 03:43, 31 October 2009 (UTC)Reply

Send the file to SeaMonkey! It's not a wikipedia problem if the PNG files are good for you. Tom Ruen (talk) 04:06, 31 October 2009 (UTC)Reply

Safari does it too. That makes the problem somewhat more ambiguous to me. I'm looking for other svg viewers to see what they show. Wurdeh (talk) 04:10, 31 October 2009 (UTC)Reply