Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

XLST processing

  • 4 replies
  • 5 have this problem
  • 2 views
  • Last reply by fobispo

fobispo
fobispo
more options

It seems like firefox is failing to treat the output of an XSLT transformation tagged as HTML, as an HTML document.

I'm attempting to use the google charts API, and I get:

Timestamp: 6/13/12 3:45:41 PM Error: uncaught exception: [Exception... "An attempt was made to use an object that is not, or is no longer, usable" code: "11" nsresult: "0x8053000b (NS_ERROR_DOM_INVALID_STATE_ERR)" location: "https://www.google.com/jsapi Line: 21"]

And it fails to draw any charts on the page. The site works correctly in both Safari and Chrome....

The page that I'm trying to see is an experimental BIND statistics page that I'm building as an in house experiment at ISC. http://polkmn.com:88

It seems like firefox is failing to treat the output of an XSLT transformation tagged as HTML, as an HTML document. I'm attempting to use the google charts API, and I get: Timestamp: 6/13/12 3:45:41 PM Error: uncaught exception: [Exception... "An attempt was made to use an object that is not, or is no longer, usable" code: "11" nsresult: "0x8053000b (NS_ERROR_DOM_INVALID_STATE_ERR)" location: "https://www.google.com/jsapi Line: 21"] And it fails to draw any charts on the page. The site works correctly in both Safari and Chrome.... The page that I'm trying to see is an experimental BIND statistics page that I'm building as an in house experiment at ISC. http://polkmn.com:88

All Replies (4)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

I see the problem, but I'm no good at reading minified JavaScript code so I can't tell which part of the code is triggering the error.

For what it's worth, the page doesn't work in IE8, either.

fobispo
fobispo Question owner
more options

I've added a full description of the bug here: 

 https://bugzilla.mozilla.org/show_bug.cgi?id=391154

Which was the result of a "fix" of another bug described here: 

 https://bugzilla.mozilla.org/show_bug.cgi?id=202765#c41

Basically it has to do with using document.write() in an XSLT generated page..

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

According to MDN, Firefox doesn't support document.write in formal xhtml, so its unavailability in xhtml generated by xml+xslt turns out to be consistent with that. See https://developer.mozilla.org/en/document.write#Notes.

fobispo
fobispo Question owner
more options

Well, not quite, I'm not generating XHTML, just plain HTML, I'm using the xsl:output option to tell the browser so..

It works correctly in Chrome and Safari.