Comment 15 for bug 1670913

It appears that symbols created in documents with scale that doesn't directly correlate to 96dpi are at the root of these issues whether used in a browser, other programs, or even Inkscape itself. So, I don't think browsers should be divorced from this report.

The sodipodi document units would be irrelevant if the scale for cm were set to the value that correlates to 96 dpi (that is 37.79527). However, the default.svg that is released in 0.92 (having display units as mm and a scale of 1 which do not correlate to 96dpi) imposes a non-standard scale and typical users will unaware that documents are non-standard until they correct the scale in the properties panel. (And plainly stated, it is beyond reasonable to expect typical users to know how and why.) When users change the units to px, in, cm, etc. the scale adjusts to remain non-standard unless explicitly changed to 96dpi or its correlates.

The simple solution is to release Inkscape with a default.svg having units=px and a scale=1:1. This is fully SVG standard document. If users change to any other display unit (mm, cm, in, etc.) the scale adjusts to a correlate value and the user need not concern themselves whatsoever and will still work with a fully standard compliant document.

Non-typical users that require a non-standard scale should have to explicitly change scale and opt-out of standard. It is beyond reasonable to expect typical users should modify scale in order to use the standard scale which they should expect to be a program default.

Considering how much effort has gone into updating Inkscape for the standard of 96dpi and the means to deal with non-standard legacy files, it's downright baffling to find that the default Inkscape configuration will create new non-standard files unless scale is modified by the user.

Regards,
TD