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

[Matthew Wilson-4]

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
_______________________________________________
dev-tech-xml mailing list
dev-tech-xml@...
https://lists.mozilla.org/listinfo/dev-tech-xml

[Martin Honnen-3]

mjwilson wrote:

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

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/
_______________________________________________
dev-tech-xml mailing list
dev-tech-xml@...
https://lists.mozilla.org/listinfo/dev-tech-xml

[Boris Zbarsky]

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
_______________________________________________
dev-tech-xml mailing list
dev-tech-xml@...
https://lists.mozilla.org/listinfo/dev-tech-xml

[Matthew Wilson-4]

On Aug 23, 8:53 pm, Boris Zbarsky <bzbar...@...> wrote:

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

I raised https://bugzilla.mozilla.org/show_bug.cgi?id=511487.

Matthew
_______________________________________________
dev-tech-xml mailing list
dev-tech-xml@...
https://lists.mozilla.org/listinfo/dev-tech-xml