为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

XLST processing

  • 4 个回答
  • 5 人有此问题
  • 2 次查看
  • 最后回复者为 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

所有回复 (4)

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.

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..

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.

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.