Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Failures from XSLT in FF3.6a1 with "body onload"

2 views
Skip to first unread message

mjwilson

unread,
Aug 16, 2009, 1:13:21 PM8/16/09
to
I have an extension (wmlbrowser.mozdev.org) which uses
nsIXSLTProcessor in an XPCOM component to transform WML content to
HTML.

In Firefox 3.6a1, the transformation fails with

[Exception... "Component returned failure code: 0x8000ffff
(NS_ERROR_UNEXPECTED) [nsIXSLTProcessor.transformToDocument]"
nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" ... ]

The error seems to be caused by "onload" on "body" in the XSL - if I
take the onload attribute away then the transform succeeds.

But if I save the WML and XSL to disk, and add in the appropriate xsl-
stylesheet PI, the transformation succeeds.

Is this a known issue, or something I should raise a bug on? The
nearest bugzillas seem to be

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

but neither seems an exact match.

Matthew

Martin Honnen

unread,
Aug 18, 2009, 11:05:51 AM8/18/09
to

File a bug, but explain whether the code worked in earlier versions of
Firefox. And a simple test case can help, if you can reproduce the
problem with transformToDocument outside of your extension code.


--

Martin Honnen
http://msmvps.com/blogs/martin_honnen/

Boris Zbarsky

unread,
Aug 23, 2009, 3:53:30 PM8/23/09
to
mjwilson wrote:
> [Exception... "Component returned failure code: 0x8000ffff
> (NS_ERROR_UNEXPECTED) [nsIXSLTProcessor.transformToDocument]"
> nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" ... ]
...
> The error seems to be caused by "onload" on "body" in the XSL

I seem to recall a bug about this going by recently, but can't seem to
locate it...

-Boris

mjwilson

unread,
Aug 24, 2009, 2:03:14 AM8/24/09
to
0 new messages