Thanks for reporting these. I've been trying to find a way to run the W3C test suite to catch such silly problems - I'll renew my efforts.

Michael Kay

On 10/06/2011 16:09, Imsieke, Gerrit, le-tex wrote:
Dear Michael,

there are two more issues:

true() gives an error, already at compile time. Declaring the following function, even without actually invoking it, will raise an error as displayed on attached screenshot (tested in Chrome 11, IE 9, FF 4).

  <xsl:function name="my:true" as="xs:boolean">
    <xsl:sequence select="true()" />

"1 cast as xs:boolean" seems to work instead (also does false()).

In addition, tokenize() seems to send the JS engines into an infinite loop. Can you reproduce this?


On 2011-06-08 09:46, Imsieke, Gerrit, le-tex wrote:
Dear Michael,

When using ixsl:eval, I always get back the argument to ixsl:eval itself.

For example, when I view in Firefox 4 or
Chrome 11, it says:

Evaluate Javascript Expressions
2 + 2 is: 2 + 2

instead of
2 + 2 is: 4

In IE 9, however, I get an XPathException.


------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking.
_______________________________________________ saxon-help mailing list archived at