Debbie Lockett
- Login: deblock
- Email: debbie@saxonica.com
- Registered on: 2014-03-13
- Last connection: 2024-12-10
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 3 | 307 | 310 |
Reported issues | 6 | 152 | 158 |
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
2024-11-28
-
Where are you looking O'Neil? https://www.saxonica.com/saxon-c/documentation12/index.html#!api/saxon_c_php_api/saxon_c_php_schemavalidator still says:
> getValidationReport()
>
> Get the validation report produced after validating t... Bug #6522: The documentation for Saxon\SchemaValidator is incorrectThe PHP `Saxon\SchemaValidator` documentation for `getValidationReport()` incorrectly states that the property to set to get a validation report as an XmlNode is `report` and not `report-node`. No mention is made there or in the document...
2024-10-31
-
I added another xslt30 test `static-032` which tests a static variable which is a sequence of different kinds of nodes (including processing instruction, and comment nodes).
SaxonJS code fix committed in Expr.js to handle `"node"` exp... Bug #4829 (Resolved): 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=...
2024-10-30
-
See also xslt30 tests `static-028, -029, -030` which currently fail with `xjcompile`. Bug #4829: 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=...
2024-10-18
-
We also use our own classes for namespace and attribute nodes (see `NamespaceNode` and `AttributeNode` in src/nsnode.js), and these are not documented (but they probably should be). Bug #5535: Improve documentation for exposed node propertiesThe documentation about XDM nodes makes reference to the fact that we've added properties to some of the node types, but doesn't actually enumerate the properties that we expect to be public.
We should use the externs for the node cla... -
Thanks for the example and additional details, I understand better what you are attempting, and hoping to achieve, now.
Yes, I'm afraid this is currently beyond the capabilities of the SaxonJS HTTP client (i.e. using `ixsl:schedule-ac... Feature #6243: Extend HTTP client to allow request body objects of other kinds (e.g. File) as accepted by the underlying APIIs there a reason why `ixsl:schedule-action/@http-request` requires a document node? IIRC it is a wrapper for `XMLHttpRequest` and it should be possible to [send non-XML data](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpReque...
2024-10-17
-
OK, so I have updated the issue to be a Feature request; but I'm going to reject it.
I think the suggestion to change the datatype for the `headers` value in the HTTP request and response maps is reasonable, but I think it is unnecess... Feature #5199 (Rejected): Multi-valued request/response headersLooks like multi-values are not supported in 2.3 because `headers` type is `map(xs:string, xs:string)`.
https://www.saxonica.com/saxon-js/documentation2/index.html#!development/http
Maybe the type should be ` map(xs:string, xs:string... -
Error message fix applied in the SaxonJS 2.7 maintenance release.
Full bug fix will be applied in SaxonJS 3.0. Bug #6506: Passing a buffer as the sourceText to SaxonJS.transform gives a nasty errorYou're supposed to pass a string, but if you pass a buffer it crashes out with a really nasty error message. We should accept a buffer and/or test that it's a string and give a reasonable error message.
-
Bug fix applied in the SaxonJS 2.7 maintenance release. Bug #6417 (Closed): Using xsl:mode on-no-match="skip" gives error Error XTDE0555 but should give XTSE0020I got sloppy when typing some XSLT 3.0 and ended up with ` <xsl:mode on-no-match="skip"/>`. While Saxon Java just tells me
```
XTSE0020 Attribute xsl:mode/@on-no-match must be
text-only-copy|shallow-copy|deep-copy|shallow-skip|... -
Bug fix applied in the SaxonJS 2.7 maintenance release. Bug #6418 (Closed): IXSL extensions which are not available on Node.jsThe documentation claims that `ixsl:set-style` and `ixsl:style()` are available in Node.js; but I think that these are actually only available in the browser. In the browser, we are dealing with an `HTMLElement` from the HTML page, which...
-
Bug fix applied in the SaxonJS 2.7 maintenance release. Bug #6516 (Closed): Expression `/[x]` is not acceptedThis bug #6473 reported against Saxon (2024-07-07), is also a bug in SaxonJS:
> The expression `/[x,y]` is apparently legal in XPath 3.1 -- it should be interpreted as the path `/` (selecting the root node) followed by an array constr...
Also available in: Atom