326636 - svg builder generate project not displayed with FireFox 1.5

Status: RESOLVED DUPLICATE of bug 307813

(Firefox :: General, defect)

Description

[alain.reutenauer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

The complete page and project was build through SVG Builder (use the demo SW if you want to generate another example)...

This is the message I get I'll translate the French part...

        Ce fichier XML ne semble pas avoir d'information de style lui étant associé. L'arbre du document est montré ci-dessous. ==> This XML file doesn't seem to have an associated style information. The document tree is shown below.
      
For further information, please use the URL.

Best regards,
   Alain R.

Reproducible: Always

Steps to Reproduce:
Just open the link... IE is OK with SVG Viewer plugin.




Use IE.

Comment 1

[Dave Townsend [:mossop]]

The svg generated does not have an association namespace and so is not technically a valid SVG image. Please see http://jwatt.org/svg/authoring/#namespace-binding

Duping this to the request to not require the namespace declaration.


*** This bug has been marked as a duplicate of 307813 ***

Comment 2

[alain.reutenauer]

(In reply to comment #1)
> The svg generated does not have an association namespace and so is not
> technically a valid SVG image. Please see
> http://jwatt.org/svg/authoring/#namespace-binding
> Duping this to the request to not require the namespace declaration.
> *** This bug has been marked as a duplicate of 307813 ***

OK, no problem for me, but it is generated by an independanr app (HTML file and all others). And the authors don't care and so do the users... I just wanted to see if FireFox worked and it doesn't.

Well, I'll tell MY users to quit FireFox.

End of discussion.

Comment 3

[Brendan Eich [:brendan]]

(In reply to comment #2)
> OK, no problem for me, but it is generated by an independanr app (HTML file and
> all others). And the authors don't care and so do the users... I just wanted to
> see if FireFox worked and it doesn't.
> 
> Well, I'll tell MY users to quit FireFox.
> 
> End of discussion.

Bye!

We will see more and more of this, not less.  Imagine if Flash had to cope with bad content generated by some popular authoring tool created and distributed by another company than Macromedia (now Adobe).  We don't provide any SVG authoring tools, and the ones people use generate content we don't handle.  The standards purity argument does not avail.

Instead of spamming bug 307813, I'll ask here whether it doesn't make sense to do what the Adobe SVG plugin does, in this particular case.  Is this a case where only the default SVG namespace is missing, not either or both of the extra two prefixed namespace declarations are missing?

/be

Comment 4

[Dave Townsend [:mossop]]

The test page now appears to be offline, but from memory, the xlink namespace was defined, the svg namespace was not, I don't know what other namespace you refer to. There was a doctype in the document though I didn't check if it was the correct doctype, but on rough inspectection it appeared to be an SVG doctype.

Comment 5

[alain.reutenauer]

put the link back online...

Comment 6

[Dave Townsend [:mossop]]

Attachment: example svg

This is the SVG in question.

Comment 7

[Dave Townsend [:mossop]]

Apologies, looking again and it seems my comment 4 was incorrect, I must have been thinking of a different bug.

Comment 8

[crf]

The file in question is only missing this
-->
xmlns="http://www.w3.org/2000/svg"
 
to announce that it is an svg file.

I guess the file was built using a program from this company --> http://www.svg-builder.com/
(Unfortunately, there are several examples on its home page of svg which have various trivial errors.)
----
I think it is a reasonable assumption that programs which create svg will feel pressured changed quite quickly to produce proper svg, particularly if firefox continues to be very strict, and firefox continues to increase its user base.

SVG is still relatively nascent.

This bug could be changed to evangelism, for I'm sure the company would be amenable to suggested improvements in its program and its home page. 

Comment 9

[alain.reutenauer]

Hi everybody,

I've contacted simalis (after you guys pinpointed the problem), they're working on it...

A complete fix will be ready for 07/2006.

Bug can be closed :-))

Regards,
   Alain.