- Login: johnSaxonica
- Email: email@example.com
- Registered on: 2013-07-04
- Last connection: 2022-04-27
Bug #5464 (Closed): unparsed-text() with an empty file throws a TypeErrorRunning in the browser (on an older version of SaxonJS2, but I suspect not) when reading in (via an `unparsed-text()` call) an empty file, there is a TypeError thrown in `Fetch.js:checkForNonXmlChars()` . Rather than an empty string bein...
I *think* I was the originator of this section of the code - I certainly wrote the original `fn:transform()` code. But it's probably about 3-4 years ago now, so I can't recall details I fear. But there must have been some reason to do th... Bug #5039: Chaining two XSLTs where the first creates a fragment with two element children works under Node.js but not in the browserWhen I run the code
const SaxonJS = require("saxon-js")
const xslt1Source = `<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
When writing the code for the XX compiler, there are so many corner cases (many thousands of them?) that might need to be satisfied that it’s pretty much impossible to cover them all. In this case during the XPath compiling of global var... Bug #5338: XX Compiler reports "Unknown accumulator NNNNN" when an accumulator-before or -after call occurs in a global variableHello, we have a pipelines and software using Saxon HE (Java) variant and the SaxonJS variant with NodeJS to build CLI tooling. We have encountered a problem in which running Saxon HE will process a collection of XSL transforms in shell ...
If I read the spec correctly
>` (//A, //B) | ()`
should return them in document order, unless some (incorrect) optimisation has elminated the empty sequence. See https://www.w3.org/TR/xpath-31/#combining_seq Support #5200: How can I check if the nodes in any XPath result are in document order? Or put them in document order?Some XPath expressions, such as
do not return the nodes in document order.
Is there a function I can call to check if the nodes are in document order? Or a function that puts them in document order?
I use XPathSelect...
It never ceases to amaze me the number of ‘corner cases’ that ‘come out of the woodwork’. When I wrote the XX processing of xsl:iterate it never occurred to me we might have a duplication of local variable and parameter names……..
... Bug #5190: xsl:iterate problem where the name of an xsl:iterate parameter duplicates the name of a local variableI was experimenting with `xsl:iterate` and found that the code
<?xml version="1.0" encoding="utf-8"?>
Are you compiling with the -ns:##html5 flag? This is often needed to allow matching html elements without namespaces... General: Event handlers not working with XX compilerUsing Saxon-JS 2.1, the event handlers don’t work in the SEF files compiled by the XX compiler.
If I download the files of the « Book List » example, and run them on my localhost, all works fine.
But if I compile the provide...
Assuming you are using SaxonJS2 then you can use saxon:timestamp() which gives the current time at the point of evaluation -
Sent from my iPad
... Support #4888: Getting current-dateTime()/js:Date() in UI/browserI have a UI in which I would like to display some duration info along side certain dates. E.g. "Today at 4:00 pm (2 minutes ago)". Implementing this in xslt is easy enough, however the UI should really update this text as time marches on...
The reason the [PUSH STATE] doesn't increment the history state length is from a typo I fear:
<xsl:variable name="json-state" select="ixsl:eval(string($js-statement/@statement))"/>
<ixsl:sequence select="js:history.pushSta... Bug #4843: js:history.pushState() has no effect?Using Saxon-JS to call [`history.pushState()`](https://developer.mozilla.org/en-US/docs/Web/API/History/pushState) does not seem to have any effect - `window.history.length` does not increment and `window.history.state` does not change:
Bug #4829 (New): Static variable initialised to node values cause run-time failureWhen compiling with the XJ compiler a static variable initialised to a node such as:
<xsl:variable name="t" static="yes" select="doc('testStatic.xml')"/>
where `testStatic.xml` is:
<foo a="1" xmlns:b="BBB" b:attribute=...
n.timezoneOffset && n.timezoneOffset !== null;
Bug #4787: Map failures with temporal keys using timezones under advanced closure compilation.When maps are merged with keys involving timezone-adjusted values, under advanced closure compiler optimisation, duplicate key errors can be raised, which are not under simple optimisation (i.e. SaxonJS2.debug.js). `map-size-014` is an e...
Also available in: Atom