Debbie Lockett
- Login: deblock
- Email: debbie@saxonica.com
- Registered on: 2014-03-13
- Last connection: 2023-06-08
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 4 | 279 | 283 |
| Reported issues | 7 | 142 | 149 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Saxon | Manager, Developer, Reporter | 2014-04-04 |
| Saxon-CE | Reporter | 2014-04-04 |
| SaxonC | Manager, Developer, Reporter | 2014-04-04 |
| SaxonJS | Manager, Developer, Reporter | 2016-08-11 |
| SaxonMirrorHE | Manager, Developer | 2021-02-02 |
Activity
2023-05-17
-
Maybe it's not actually surprising that the mechanism for aborting HTTP requests is not actually available in Node.js: what would that actually look like? The mechanism works in the browser with user interaction; but we don't actually ha... Bug #6037: ixsl:schedule-action return objectsIn SaxonJS 2, `ixsl:schedule-action` with the `document` attribute is available on Node.js. However the documentation says that the instruction "returns immediately with an object containing any associated JavaScript XMLHttpRequest (XHR)...
2023-05-12
-
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 o... Bug #6037: ixsl:schedule-action return objectsIn SaxonJS 2, `ixsl:schedule-action` with the `document` attribute is available on Node.js. However the documentation says that the instruction "returns immediately with an object containing any associated JavaScript XMLHttpRequest (XHR)...
-
In SaxonJS 2, `ixsl:schedule-action` with the `document` attribute is available on Node.js. However the documentation says that the instruction "returns immediately with an object containing any associated JavaScript XMLHttpRequest (XHR)...· Created issue
2023-05-04
-
Can now confirm that the new XSLT30 tests `evaluate-051` and `evaluate-052` also pass with SaxonJS 2. Bug #6011: Inline function created using xsl:evaluateSame bug as #6003, but on SaxonJS.
-
With these code fixes, the supplied test runs without error in SaxonJS 2. I have also verified that the test Martin supplied for bug #6004 also runs correctly in SaxonJS 2. (I have not yet run Mike's XSLT30 test because I don't see it co...· Closed issue
-
To avoid this type checking error, I think it is necessary to be less specific for the types of the arguments in the XPath function declarations in evaluationTest.xml:· Commented on issue
* use `function($instance as element()) as element(side)` instead ... -
As reported by Martin, the failure with SaxonJS 2 is different:· Commented on issue
```
xslt3 -t -s:Downloads\evaluationTest.xml -xsl:Downloads\validation.xslt
SaxonJS 2.5 from Saxonica
Node.js version v16.17.1
Compiling stylesheet C:\Users\marti\Dow...
2023-05-03
-
Fix committed on saxon11, saxon12, and main branches.
Saxon 11 and 12 dotnetdoc documentation updated online (XML and HTML versions). Bug #6010 (Closed): XPath and XSLT 4.0 language support not documented in SaxonCS .NET API docsXPath 4.0 and XSLT 4.0 are supported from Saxon 11, so the documentation for `XPathCompiler.XPathLanguageVersion` and `XsltCompiler.XsltLanguageVersion` should be corrected. (Note that the documentation for `XQueryCompiler.XQueryLanguage... -
XPath 4.0 and XSLT 4.0 are supported from Saxon 11, so the documentation for `XPathCompiler.XPathLanguageVersion` and `XsltCompiler.XsltLanguageVersion` should be corrected. (Note that the documentation for `XQueryCompiler.XQueryLanguage...· Closed issue
2023-04-27
Also available in: Atom
.