Created attachment 803722 [details] svg referencing another svg using image tag User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36 Steps to reproduce: Created an SVG (test1.svg) that references another SVG (movie.svg) using the image tag. Also, the outer SVG contains a rectangle with the same size as the inner image. Also created an SVG (test2.svg) in which the inner SVG is scaled. Actual results: The referenced SVG appears too small. When zooming in on the SVG, the referenced SVG stays the same size. The bounding box of the referenced SVG is incorrect. If the image is scaled, it appears blurred at some zoom levels. Expected results: The inner SVG should be as big as the rectangle. It should fit its bounding box that is visible when hovering over the image element in the web developer tool. If the image is scaled, it should appear crisp, not blurred. Normal behavior in Chrome, IE and old Firefox versions.
Created attachment 803725 [details] image tag scaled by surrounding g In this image, the movie icon appears blurred in Firefox 23.
Comment on attachment 803722 [details] svg referencing another svg using image tag In this image, the movie icon has the wrong size in Firefox 23. Also it does not scale when zooming.
Created attachment 803729 [details] svg referencing another svg using image tag
Created attachment 803731 [details] image tag scaled by surrounding g
The scaled image is crisp on Trunk (that issue is fixed in Firefox 24). The image size is exactly the same in Opera as it is in Firefox so I suspect that part of this issue is invalid which and that leaves us with zooming not zooming the embedded SVG image which is a bug so we'll make this bug about that, especially as we can only have one issue per bug. So STR are zoom the document and the image should zoom along with it but at the moment it doesn't.
Actually the zooming works on trunk too so all of this works. Feel free to try a nightly to confirm: http://nightly.mozilla.org/
I agree, both issues are fixed in Firefox 24. Thanks.