No xsltLineNr in the browser while it exists with Node.js

I am trying to run XSLT 3 by calling fn:transform from SaxonJS.XPath.evaluate, when I do this with Node any runtime error encountered during XSLT transformation seems to be thrown with an exception having an xsltLineNr property.

However, inside the browser the exception raised doesn't seem to have any such property.

Is that intentional?

Replies (1)

RE: No xsltLineNr in the browser while it exists with Node.js - Added by Michael Kay over 4 years ago

On Node.js we parse documents using SAX and DOM libraries that allow us to capture the line number and insert it as a custom property into the DOM Node. This possibility doesn't exist in the browser, where we use the DOM implementation provided by the browser vendor.

(1-1/1)

Please register to reply

Project

Profile

Help

Saxon » SaxonJS