295581 - nsSVGDocument doesn't implement nsIDOM3Document

Status: RESOLVED DUPLICATE of bug 226193

(Core :: SVG, defect)

Description

[Thomas Keller]

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

I use to "find" implemented functions of DOM objects by using
the following code. This works perfectly for (X)HTML documents
in FF:

<svg ... onload="init(evt)">
<script>
function init(my_evt) {
    var func = "";
    for (i in my_evt) {
        func += my_evt[i] + "\n";
    }
    alert(func);
}
</script>
...
</svg>

For the SVG document above the following exception is fired:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIDOM3Document.domConfig]"  nsresult:
"0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame ::
file:///H:/projects/mmt2/SVG/animation.svg :: init :: line 18"  data: no]

Reproducible: Always

Comment 1

[Thomas Keller]

Ohh... btw... this was DeerPark Alpha 1 =)

Comment 2

[Hermann Schwab]

Can you add a minimal testcase? If you need more than 1 file, attach the
referred files first, get the URL from the Attachment box and insert this where
it is needed.

Create a New Attachment:
https://bugzilla.mozilla.org/attachment.cgi?bugid=295581&action=enter

Comment 3

[Thomas Keller]

Attachment: When for (i in svgObject) is reached, the exception fires.

Comment 4

[Jonathan Watt [:jwatt]]

The for-in statement is core JavaScript, not SVG, and it's implemented fine. If
you change your loop to:

    for (i in my_evt) {
      if (i != 'domConfig')
        func += my_evt[i] + "\n";
    }

it should manage to enumerate the document's properties for you without any
further errors. The problem you've encountered is that nsSVGDocument doesn't
implement the interface nsIDOM3Document. Changing the summary to say so and
confirming.

Comment 5

[Boris Zbarsky [:bzbarsky]]

not an svg-speficic issue, even.

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