Saxon » SaxonJS

Furthermore, on the SaxonJS 3 development branch, the implementation of ixsl:schedule-action has been updated to use the Fetch API for HTTP requests and document fetching, both in the browser and on Node.js. Rather than returning XHR objects, we return AbortControllers, on Node.js as well as in the browser (enabling use of the aborting mechanism). So while ixsl:schedule-action/@document returns an empty sequence with SaxonJS 2 on Node.js; it returns an object in SaxonJS 3. We give advice to throw away the result of an ixsl:schedule-action instruction to prevent it being written to the current result tree (https://www.saxonica.com/saxon-js/documentation2/index.html#!ixsl-extension/instructions/schedule-action); but it is easy to make this mistake (see the current failure of nodejs unit test schedule-009), and potentially even more so with this change between SaxonJS 2 and 3.

Perhaps we can amend the implementation so that the instruction only returns objects when we are not writing to the current result tree (i.e. when context.tempOutputState !== false); so it always just returns an empty sequence when writing to the current result tree.

Documentation updates committed on the saxonjs2 branch to clarify the status when using ixsl:schedule-action in Node.js with SaxonJS 2.

Updates committed on the main branch to explain the changes to ixsl:schedule-action in SaxonJS 3.

Bug fix applied in the SaxonJS 2.6 maintenance release.