Version: 22.0.1
Steps: When I create an illustration or import an illustration and then run Export As or Export for Screens the SVG file it generates is not including the encoding tag.
Expected result: Fully qualified SVG file.
Actual result: Incomplete SVG file.
Why it matters: When trying to embed svg files in a web page through <img src="svg-file.svg"> or <embed> browsers fail to load the file as an asset when the <xml> encoding tag is missing.
Yes the Save As route worked. It does include the encoding tag. So the question now is…why don't the other export options included the xml encoding tag when they are probably the more common workflows for exporting assets for web and screens?
Taylor
Version: 22.0.1
Steps: When I create an illustration or import an illustration and then run Export As or Export for Screens the SVG file it generates is not including the encoding tag.
Expected result: Fully qualified SVG file.
Actual result: Incomplete SVG file.
Why it matters: When trying to embed svg files in a web page through <img src="svg-file.svg"> or <embed> browsers fail to load the file as an asset when the <xml> encoding tag is missing.
Yes the Save As route worked. It does include the encoding tag. So the question now is…why don't the other export options included the xml encoding tag when they are probably the more common workflows for exporting assets for web and screens?