Saxonica Developer Community

2020-04-03

• 
  Debbie Lockett Saxon-JS

  13:12 · Closed issue

  All dynamic loading of internal resources has been eliminated for Saxon-JS 2.0. The internal resources which were dynamically loaded as required for Saxon-JS 1.x (opt/functions.json, opt/categories.json, and lib/xpath/XPathJS.min.j) will... Feature #3462 (Resolved): Asynchronous fetch for internal resources

  We currently use synchronous fetches for Saxon-JS internal resources: opt/functions.json used by function-available(); opt/categories.json used for some advanced regex; and lib/xpath/XPathJS.min.js. But we should use asynchronous fetches...

2020-03-30

• 
  Debbie Lockett Saxon

  18:53 · Closed issue

  Marking closed, as 10 documentation has been updated online (XML and HTML versions). Bug #4497 (Closed): Wrong default type for tuple fields in the Saxon 10 documentation.

  In the Saxon 10 documentation, it states that if an `as` clause is absent then the type of that field is `item()*` instead of `item()+`. The current wording would (according to condition 2) permit the field to be absent (as it would allo...

2020-03-27

• 
  Debbie Lockett Saxon

  19:29 · Commented on issue

  Documentation changes copied and committed on 9.9 branch.
  Online documentation for 9.9 and 10 updated (XML and HTML versions). Bug #4486: Attribute saxon:explain doesn't work

  According to the documentation, it should be possible to say saxon:explain="yes" on `xsl:template` or `xsl:function` to get optimizer diagnostics for that template or function.
  This isn't working, on either 9.9 or 10.0.
  The basic ...
• 
  Debbie Lockett Saxon-JS

  10:52 · Edited issue

  Yes, you need to be careful using relative URIs. Please see the information under "Relative URIs" at http://www.saxonica.com/saxon-js/documentation/index.html#!development/source-documents. In particular, the last paragraph:
  "We recom... Support #4491 (In Progress): Saxon-JS cannot locate the document('/floorplan.svg') path relative ...

  When I use the document() function in saxon-js to try to access a relative file path on the web server It cannot find the path as I expected and I need to put a full path in with the domain to make it work. I think this may be a bug or i...

2020-03-26

• 
  Debbie Lockett Saxon-JS

  17:15 · Commented on issue

  The problem is indeed dynamic loading of Saxon-JS internal resources (lib/xpath/XPathJS.min.js, and the contents of the 'opt' directory).
  For Saxon-JS 2.0, we have got rid of this dynamic loading; everything is in-built. So hopefully ... Bug #4103: Saxon-JS dynamic loading errors > it won't run on Tizen OS in a webapp browser (on Sma...

  Hi Guys,
  Thanks for creating the Saxon-JS product which is a great product! Although I have had a lot of success running it in conventional browsers I wanted to report Saxon-JS failing to run in the Tizen OS (linux based) web browser ...
• 
  Debbie Lockett Saxon-JS

  17:10 · Closed issue

  Hi Gary, this actually looks to be the same issue which you raised some time ago (#4103). But fair enough that because we have failed to respond, or provide updates there that you raised it again!
  Saxon-JS 2.0 will indeed do away with... Feature #4492 (Duplicate): Saxon-JS cannot find '/lib/xpath/XPathJS.min.js' dependency running on...

  I cannot run saxon-js on the Samsung Web browser on the TVs and smartwatches and think this should work as the browser there is based on the chromium browser...
  The root cause appears to be that Saxon-JS cannot find the path for the ...

2020-03-23

• 
  Debbie Lockett Saxon

  17:07 · Closed issue

  10 documentation app updated online: SEF update, and revert to use Saxon-JS 1.2.
  Changes committed in userdoc on dev branch.
  Marking as resolved because the online javadoc search does now work.
  But not closing because the saxon-... Bug #4487 (Resolved): 10 documentation app javadoc search is broken

  It should be possible to search the javadoc for class and method names, etc. by prefixing search terms with '#'. This doesn't seem to be working. The app just hangs.
  It might be because the dotnetdoc isn't there, or there could be som...
• 
  Debbie Lockett In fact the reason seems to be "all of the above":
  1. The missing dotnetdoc files is the first issue. This requires a temporary change in the findtext.xsl app stylesheet, to only try to search javadoc for now (while Saxon 10 is only a...

  13:53 · Edited issue

2020-03-20

• 
  Debbie Lockett Saxon

  19:14 · Created issue

  Bug #4487 (Resolved): 10 documentation app javadoc search is broken

  It should be possible to search the javadoc for class and method names, etc. by prefixing search terms with '#'. This doesn't seem to be working. The app just hangs.
  It might be because the dotnetdoc isn't there, or there could be som...
• 
  Debbie Lockett Saxon

  17:03 · Closed issue

  Relevant content changes also now made and committed in 9.9 documentation, for the following pages:
  * extensibility/config-extend/uri-resolution/collection-uri-resolver
  * functions/fn/collection, uri-collection
  * sourcedocs/collecti... Bug #4484 (Closed): Documentation of fn:collection()

  The status section of the documentation for fn:collection() (in the Function Library chapter) refers to the old `CollectionURIResolver` interface, which is deprecated in 9.9 and withdrawn in 10.0. It should be updated to refer to the new...