Saxonica Developer Community

2024-11-28

• 
  Debbie Lockett SaxonC

  11:56 · Commented on issue

  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 incorrect

  The 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

• 
  Debbie Lockett SaxonJS

  12:51 · Closed issue

  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 failure

  When 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

• 
  Debbie Lockett SaxonJS

  11:53 · Commented on issue

  See also xslt30 tests `static-028, -029, -030` which currently fail with `xjcompile`. Bug #4829: Static variable initialised to node values cause run-time failure

  When 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

• 
  Debbie Lockett SaxonJS

  18:32 · Commented on issue

  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 properties

  The 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...
• 
  Debbie Lockett SaxonJS

  12:48 · Commented on issue

  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 API

  Is 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

• 
  Debbie Lockett SaxonJS

  18:05 · Closed issue

  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 headers

  Looks 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...
• 
  Debbie Lockett SaxonJS

  15:47 · Commented on issue

  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 error

  You'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.
  
• 
  Debbie Lockett SaxonJS

  15:45 · Closed issue

  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 XTSE0020

  I 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|...
• 
  Debbie Lockett SaxonJS

  15:45 · Closed issue

  Bug fix applied in the SaxonJS 2.7 maintenance release. Bug #6418 (Closed): IXSL extensions which are not available on Node.js

  The 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...
• 
  Debbie Lockett SaxonJS

  15:45 · Closed issue

  Bug fix applied in the SaxonJS 2.7 maintenance release. Bug #6516 (Closed): Expression `/[x]` is not accepted

  This 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...