Comment #3 on issue 8424 by Sebastian.von.Knorring: SVG image is not properly rendered http://code.google.com/p/chromium/issues/detail?id=8424
Ah, looking closer into this revealed something. In the XML notation of the SVG file there are shape definitions like the following: <line x1="769.0" y1="519.9" x2="785.9" y2="440.6"/> <line x1=" 64.0" y1="206.0" x2=" 31.0" y2="280.1"/> <line x1="111.7" y1="140.4" x2=" 64.0" y2="206.0"/> In other words, coordinate values that are less than one hundred have a space appended to them, within the quotation marks that delimit the value. This is apparently because then the values "align" column-wise with the rest of the shape definitions. It's pretty-printing of XML notation. Doing a global search for '=" ' and replacing with '="' and then saving and re-testing the file reveals that Chrome displays then the file OK. So all coordinate values less than one hundred that consequently contain a space character are not parsed properly by Chrome and the distortion in the top and left edges appears since the values remain effectively the default value which appears to be zero. The question is now, is this valid SVG per the SVG spec? A few data points: - The open-source image manipulation program Inkscape displays the unedited "broken" file OK. - The SVG file contains the following comment: "Created with svg-rocco-library" -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
