Closed Bug 301921 Opened 19 years ago Closed 19 years ago

cannot see SVG files

Categories

(Core :: SVG, defect)

Product:
Core
Component:
SVG
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: baffclan, Unassigned)

References

(
URL
)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050723 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050723 Firefox/1.0+

cannot see SVG files


Reproducible: Always

Steps to Reproduce:
1. open about:config, svg.enabled set a true (default)
2. open http://www.adobe.com/svg/demos/main.html

Actual Results:  
cannot see SVG files

Expected Results:  
can see SVG files

SVG is enable?
open about:buildconfig, "--enable-svg" Configure arguments
Not a mozilla issue, reason for this is that they check if a svg plugin is
installed:
http://www.adobe.com/svg/viewer/install/auto/svgcheck.js
http://www.adobe.com/svg/demos/svgbubbles/chart/chart.svg

Firefox/2005030706-trunk/WinXP can see SVG file.
however, Firefox/2005072306-trunk/WinXP cannot see SVG file.
displayed XML error

XML Parsing Error: prefix not bound to a namespace
Location: http://www.adobe.com/svg/demos/svgbubbles/chart/chart.svg
Line Number 4, Column 2:

	<animate id="D74a62e4" xlink:href="#V74a62e4"  dur="indefinite"/>
--------^


Confirming, doesn't work with Firefox 1.5 beta1 (Linux, binary build from
mozilla.org), I get

XML Parsing Error: not well-formed
Location: http://www.adobe.com/svg/demos/chart.svgz
Line Number 1, Column 1:
&#65533;
^
Same thing on a MAcOSX build : 
User-Agent : Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4)
Gecko/20050908 Firefox/1.4

When trying to view the Chart and graph demo at
http://www.adobe.com/svg/examples.html

XML Parsing Error: not well-formed
Location: http://www.adobe.com/svg/demos/chart.svgz
Line Number 1, Column 1:&#65533;
^

Apparently all sgvz generated files are not handled correctly.
@ comment #2 : the problem is that adobe is sending non valid XML, the xlink
namspace is not bound in that document.

@ comment #3 , #4 :
the problem with the svgz files is that they are not served with the appropriate 
content-encoding header. so Adobe uses a wrongly configured server.

both are not mozilla errors. so marking this bug as invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.