Saxonica Developer Community

2021-02-18

• 
  Debbie Lockett Saxon-JS

  19:24 · Commented on issue

  See Saxon API tests: async-trans-028b, async-trans-029b, async-trans-030b.
  Note that it is possible to avoid this problem with strong conversion by using `SaxonJS.atom`, e.g. the following works:
  ~~~ javascript
  "stylesheetParams": ... Bug #4914: Parameters supplied in SaxonJS.transform options not converted correctly for typed array required types

  Using the `stylesheetParams` option for `SaxonJS.transform`, strong conversion (as documented at https://www.saxonica.com/saxon-js/documentation/index.html#!xdm/conversions) for a stylesheet parameter with a typed array required type (i....
• 
  Debbie Lockett Using the `stylesheetParams` option for `SaxonJS.transform`, strong conversion (as documented at https://www.saxonica.com/saxon-js/documentation/index.html#!xdm/conversions) for a stylesheet parameter with a typed array required type (i....

  18:57 · Created issue

2021-02-17

• 
  Debbie Lockett Saxon-JS

  18:53 · Closed issue

  Further fixes committed, so that parseXmlFromString now has 3 consistent arguments. Bug #4830 (Resolved): HTML response from ixsl:schedule-action is parsed as XML, causing failure

  (Reported by Martynas Jusevičius <martynas@atomgraph.com> on saxon-help mailing list on 2 Nov 2020).
  Saxon receives an HTTP response with content type text/html and attempts to parse it as XML, causing a failure FODC0002.
  In this p...
• 
  Debbie Lockett Reopening as I'm seeing some new failures for fn-transform tests in the browser (e.g. fn-transform-4), which look to be caused by the changes. The Platform.parseXmlFromString method already has a second argument (lineNumbering) defined f...

  18:33 · Edited issue

2021-02-11

• 
  Debbie Lockett Saxon-JS

  13:50 · Closed issue

  Confirm the fix works and has been tested (collations-1006 now passes). Bug #4616 (Resolved): default-collation

  If an [xsl:]default-collation attribute appears in the stylesheet, the XX compiler appears to ignore it.
  Given the input
  ~~~
  <xsl:copy-of select="saxon:highest($data, my:val#1)"
  default-collation="http://www.w3.org...
• 
  Debbie Lockett Saxon-JS

  12:40 · Closed issue

  Code fix was committed on 2021-02-03 to pass the tests (but I hadn't actually realised this bug existed):
  ~~~ javascript
  n.timezoneOffset !== undefined && n.timezoneOffset !== null;
  ~~~
  Bug #4787 (Resolved): 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...

2021-01-12

• 
  Debbie Lockett Saxon-JS

  12:14 · Closed issue

  Marking closed. Presumably the the secondary issue was resolved by the user, as no further information has been supplied here. Support #4790 (Closed): SaxonJS setup

  Hello,
  After downloading SaxonJS, I can't find the xslt3 command-line interface.
  TIA,
  Robert.
  

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