Saxonica Developer Community

2020-10-30

• 
  Debbie Lockett Saxon-JS

  11:21 · Commented on issue

  I'm sure we have considered whether such an extension - which converts XDM maps to JavaScript object literals - would be useful (or was necessary) before; but perhaps not formally. One difficulty with this of course is that IXSL extensio... Bug #4815: Conversion of XDM maps to JS objects

  On the XML.com Slack general channel, Pieter Lamers asked the following:
  > I'm trying to get scrollIntoView to work smoothly. Now, `ixsl:call($target, 'scrollIntoView',[])` works, but I don't know how to pass the `ScrollIntoViewOption...
• 
  Debbie Lockett On the XML.com Slack general channel, Pieter Lamers asked the following:
  > I'm trying to get scrollIntoView to work smoothly. Now, `ixsl:call($target, 'scrollIntoView',[])` works, but I don't know how to pass the `ScrollIntoViewOption...

  11:05 · Created issue

2020-10-27

• 
  Debbie Lockett Saxon

  17:08 · Closed issue

  QT3 method-adaptive tests amended to allow optional XML declaration when serializing nodes.
  Patch committed in `AdaptiveEmitter` class on 10.x and 11.x trunk branches. Bug #4647 (Resolved): omit-xml-declaration for adaptive serialization

  For adaptive serialization, setting the `omit-xml-declaration` parameter has no affect. XML declarations are never output when serializing nodes, so in effect the default is "true", and setting the parameter to "false" has no affect (i.e...
• 
  Debbie Lockett In `AdaptiveEmitter.serializeNode()`, the `"omit-xml-declaration"` property is unconditionally being set to `"yes"`. This is why setting the output parameter has no affect (it is always overwritten). This code should be patched to only s...

  15:11 · Edited issue

2020-10-02

• 
  Debbie Lockett Saxon-JS

  11:48 · Closed issue

  Rather than needing to copy the `localVars`, there is an `assembleParams` method which is supposed to handle this ("Assemble parameters for a template call using call-template, apply-templates, apply-imports, or next-match"). The problem... Bug #4767 (Resolved): xsl:with-param value evaluation in xsl:call-template in ixsl:schedule-action

  In a situation like this
  ```xml
  <xsl:for-each select="$sequence">
  <xsl:variable name="item" select="." as="element()"/>
  <ixsl:schedule-action http-request="map{ ... } }">
  <xsl:call-template name="callback">
  ...

2020-10-01

• 
  Debbie Lockett Saxon-JS

  13:15 · Edited issue

  I've created some JS2 unit tests to reproduce the bug, and test the issue. I'm actually also seeing some difference in behaviour here between XX SEFs (generated by Saxon-JS 2 on Node.js) and XJ SEFs (generated with Saxon-EE 10).
  Test ... Bug #4767 (In Progress): xsl:with-param value evaluation in xsl:call-template in ixsl:schedule-action

  In a situation like this
  ```xml
  <xsl:for-each select="$sequence">
  <xsl:variable name="item" select="." as="element()"/>
  <ixsl:schedule-action http-request="map{ ... } }">
  <xsl:call-template name="callback">
  ...

2020-09-29

• 
  Debbie Lockett Saxon-JS

  15:04 · Closed issue

  Glad to hear you've got the upgrade to Saxon-JS 2 pretty much done now! And that the custom handling for sending `FormData` with JavaScript is working. I'm now closing this support issue.
  I've added more detail in issue #4735 about th... Support #4732 (Closed): Upgrading AtomGraph application from Saxon-CE to Saxon-JS 2

  As explained on the mailing list, I am trying to replicate the behavior of Saxon-CE's [`updateHTMLDocument()`](https://www.saxonica.com/ce/user-doc/1.1/index.html#!api/xslt20processor/updateHTMLDocument) with Saxon-JS 2. This code is inv...
• 
  Debbie Lockett Saxon-JS

  14:04 · Commented on issue

  For the specific problem with sending `FormData` by HTTP (as raised in Support issue #4732), there is a JavaScript work around which could be an option, except it is not currently possible with the Saxon-JS HTTP client (`ixsl:schedule-ac... Feature #4735: Add multipart support in HTTP client

  As documented, multipart HTTP requests and responses are not currently supported properly by the Saxon-JS HTTP client (`ixsl:schedule-action/@http-request`).
  See https://www.saxonica.com/saxon-js/documentation/index.html#!development/...

2020-09-24

• 
  Debbie Lockett Saxon-JS

  18:30 · Closed issue

  Replaced all use of `&#8209;` in the Saxon-JS 2 documentation.
  Changes committed and updated online. Bug #4751 (Closed): Use of non-breaking hyphen in command line documentation

  In the Node.js command line documentation at https://www.saxonica.com/saxon-js/documentation/index.html#!nodejs/command-line, we use the non-breaking hyphen character `&#8209;` to improve the look of the options in the table, and prevent...
• 
  Debbie Lockett In the Node.js command line documentation at https://www.saxonica.com/saxon-js/documentation/index.html#!nodejs/command-line, we use the non-breaking hyphen character `&#8209;` to improve the look of the options in the table, and prevent...

  18:17 · Closed issue