641303 - SVG in data uri rendered differently to relative linked svg

Status: RESOLVED DUPLICATE of bug 243917

(Core :: SVG, defect)

Description

[Emil Langrock]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0) Gecko/20110310 Firefox/4.0 Iceweasel/4.0

The output of the renderer differs between svg that it is linked using an external file and embedded using data uris.

I noticed that mozilla also renders it wrong when using an external file, but the data uri version is completely unreadable. I will attach a tarball with example files and the rendering that i see.

Reproducible: Always

Comment 1

[Emil Langrock]

Attachment: Example files and renderings for data-uri/external images + reference rendering

Comment 2

[Alice0775 White]

Maybe duplicate of Bug 243917

Comment 3

[Robert Longson [:longsonr]]

Can you upload individual files rather than a tarball please?

Comment 4

[Emil Langrock]

Attachment: SVG reference rendering

Comment 5

[Emil Langrock]

Attachment: Firefox rendering of external svg

Comment 6

[Emil Langrock]

Attachment: Firefox rendering of svg from data uri

Comment 7

[Emil Langrock]

Attachment: HTML with included data uri svg

Comment 8

[Emil Langrock]

Attachment: HTML which uses external svg

Comment 9

[Emil Langrock]

Attachment: External svg used by external_svg.xhtml

Comment 10

[Emil Langrock]

Attachment: HTML which uses external svg

Comment 11

[Boris Zbarsky [:bzbarsky]]

You're using things like |fill: url(#green2grey)|.  This resolves the url relative to the data URI, so you get something equivalent to: |fill: url(data:.....#green2grey)| which is of course not valid SVG, and can't render, if the "#green2grey" part is treated as part of the data.  Which it is with data: in Gecko.

There is an existing bug on this; fixing it requires redefining the data: spec a bit, last I checked.

Comment 12

[Daniel Holbert [:dholbert]]

(In reply to comment #11)
> There is an existing bug on this

Yup -- duplicate of Bug 243917, as Alice0775 suggested in Comment 2.