309399 - handling of 'application/rdf+xml' changed since 1.0

Status: RESOLVED DUPLICATE of bug 256084

(Core Graveyard :: RDF, defect)

Description

[Stefano Mazzocchi]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+

Firefox 1.0 allowed extensions to hook up content handlers for pages that
returned with "application/rdf+xml" mime type. Since deerpark, the content is
intercepted by the by the browser content handler and treated as XHTML,
preventing extension's content handler from being invoked and provide a
different use of that data.

Reproducible: Always

Steps to Reproduce:
1. load any page that is served with "application/rdf+xml" mime-type (for
example http://simile.mit.edu/piggy-bank/doap.rdf or
http://www.w3.org/People/EM/contact)

Actual Results:  
Firefox 1.0 will ask you what to do with it or, if an extension hooks up a
handler, it will be invoked

Firefox 1.1a-1.5b will render it as XHTML and the extension listener is never called

Another problem is that 'document.contentType' is not 'application/RDF+XML' as
it should be but it's still 'application/vnd.mozilla.xul+xml', preventing
extensions from reacting on load of RDF/XML content even after the loading has
been processed.


Expected Results:  
Firefox 1.5 should behave like Firefox 1.0 and avoid treating RDF/XML content as
XHTML one.

Comment 1

[Phil Ringnalda (:philor)]

That was bug 61839, which very nearly meant you wouldn't have gotten it in 1.0 -
jst apparently wanted to land it for 1.0, but nobody remembered to ask for
branch approval. I rather doubt that you can have it back, since I think part of
the weirdness with the XUL mime-type is from internal use, but you'll certainly
need to be in a Core bug somewhere. I guess since the RDF product tooketh,
that's the place.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Actually, if an extension wants to render this type it can -- it just needs to add the right things to the Gecko-Content-Viewers XPCOM category (or remove the entries already in it, and install a content converter if it wants to).

Note that we render application/rdf+xml as XML, not XHTML.  Not the same thing.

Comment 3

[Stefano Mazzocchi]

(In reply to comment #2)
> Actually, if an extension wants to render this type it can -- it just needs to
> add the right things to the Gecko-Content-Viewers XPCOM category (or remove the
> entries already in it, and install a content converter if it wants to).

Boris, thanks for your reply.

I've tried to do those "right things" but they didn't work, so probably I'm doing something wrong. Can you point me at some documentation or, even better, some javascript code that allows me to that? 

Thanks much in advance.