Saxon » SaxonJS

While working on the documentation app, a problem was discovered to do with using ixsl:schedule-action in a template, but not as the final construct. If a parameter (whose value is changed by some page interaction) is used again after it has been used within ixsl:schedule-action, then the value can come out wrong on subsequent interactions. For example, something like the following:

<xsl:message>before $hash-parts {$hash-parts}</xsl:message>
                <ixsl:schedule-action document="{$jpackage-path}">
                    <xsl:call-template name="package-page">
                        <xsl:with-param name="package-path" select="$jpackage-path"/>
                        <xsl:with-param name="hash-parts" select="$hash-parts"/>
                    </xsl:call-template>
                </ixsl:schedule-action>
   <xsl:message>after $hash-parts {$hash-parts}</xsl:message> 

The problem is that within the code for ixsl:schedule-action (in Expr.js), the new context for the called template is constructed using:

c2 = context.newContext(false);

when we should be using

c2 = context.newContext(true);

to ensure that parameters are cleared.