Re: [xsl] Opera's JavaScript API for XSLT?

["Michael(tm) Smith" <mikes@xxxxxxxxx>]

Robert Koberg <rob@xxxxxxxxxx>, 2006-09-27 07:41 -0400:

> Michael(tm) Smith wrote:
> >Note that lack of support for the XSLT document() function in
> >Opera's implementation is a known issue. 
> 
> OK. That is where it is failing. The debug info I received for the 
> failure is at the end of the email.

I see.

> Is document() going to be added at some point?

Yes, absolutely. I wish I could say exactly when, but I don't know.

> My use case is that in some transformations I use a
> configuration or simple stub ('<x/>') XML file as the main
> source and pull in other files based on the config or
> parameters. This way you get around loading a big dom in JS and
> only load a processor optimized dom for the transformation.

Sounds like a perfectly valid use case. I find the lack of
document() support to be a fairly big obstacle myself. But then
(at least in the work I do with XSLT) I guess I also find lack of
support for turning XSLT 1.0 result-tree fragments into real node
sets to be a equally big obstacle. Opera 9.02 does do the right
thing there by supporting exslt:node-set().

> If you want to check out the dojo implementation, you would need to get 
> the trunk from SVN (or wait till .4 comes out, which should be soon). In 
> the dojo/tests/xml/ directory you will find test_XslTransform.html which 
> has 3 example transformations. The first one uses the document function 
> and therefore fails. The other two do not use document() and work as 
> expected.

OK. I'll check the sources from SVN and try it myself. But I do
know for certain that any test case which relies on document() is
currently going to fail in Opera.

> I will let the dojo folks know about the document() limitation.

Thanks. And as soon as support for document() is finally added, I
can guarantee you that Opera will be announcing it widely to the
developer community.

  --Mike