Saxonica Developer Community

2021-07-23

• 
  Debbie Lockett Saxon-JS

  17:32 · Closed issue

  Closing this issue with no action; the `ixsl:contains` function is behaving as expected. Bug #5040 (Rejected): ixsl:contains() returns true for missing 'value' property

  I made a [test](https://namedgraph.github.io/saxon-js2-test/) that handles `ixsl:onclick` for an empty input (`<input id="empty-value"/>`). The stylesheet is [here](https://namedgraph.github.io/saxon-js2-test/client.xsl).
  Calling `ixs...

2021-07-22

• 
  Debbie Lockett Saxon-JS

  17:38 · Commented on issue

  Committed:
  * Saxon-JS code changes (in ExtraFn.js and lib/xpath/xsltData.js)
  * New selenium browser tests: ixsl/get20; ixsl2/getlookup20, getlookup20b
  * Updated results for tests ixsl/getEmpty01, getEmpty02, getEmpty04
  These now a... Bug #5046: Handling null and undefined objects in ixsl:get() and ixsl:set-property

  (Having already spent lots of time working on this, it's time to try to get the issues in writing.)
  We need to clarify how `null` and `undefined` JavaScript objects are handled within `ixsl:get()` and `ixsl:set-property`. Both the cod...
• 
  Debbie Lockett If we amend the definition of `ixsl:get()` to say that the supplied object must exist (i.e. not be null or undefined in JavaScript), then this brings the function better in line with `ixsl:call`, `ixsl:contains()` and `ixsl:set-property`...

  16:53 · Commented on issue
• 
  Debbie Lockett The proposed solution is that we should throw an error if we ever attempt to get a property of null or undefined. This is indeed what happens in JavaScript. So if at any point prior to the last step, while stepping down a chain of nested...

  16:32 · Commented on issue
• 
  Debbie Lockett (Having already spent lots of time working on this, it's time to try to get the issues in writing.)
  We need to clarify how `null` and `undefined` JavaScript objects are handled within `ixsl:get()` and `ixsl:set-property`. Both the cod...

  16:27 · Created issue

2021-07-15

• 
  Debbie Lockett Saxon-JS

  12:02 · Commented on issue

  Yes, it looks like an `HTMLInputElement` always has a `value` property: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement
  So I'm afraid the `ixsl:contains()` result is right. Can you instead just do a check whether the v... Bug #5040: ixsl:contains() returns true for missing 'value' property

  I made a [test](https://namedgraph.github.io/saxon-js2-test/) that handles `ixsl:onclick` for an empty input (`<input id="empty-value"/>`). The stylesheet is [here](https://namedgraph.github.io/saxon-js2-test/client.xsl).
  Calling `ixs...

2021-07-08

• 
  Debbie Lockett Saxon-JS

  16:57 · Edited issue

  Again, Martin is correct that the problem arises from your use of dot characters in the property names. Effectively Saxon-JS does not allow property names to include dot characters (instead these are used as separators for nested propert... Bug #5031 (In Progress): ixsl:set-property: ... not found for supplied object

  This might not be a bug, just me not understanding the error message.
  I have the following code which _usually_ works fine:
  ```
  <xsl:message>AAAA $content-uri: <xsl:value-of select="$content-uri"/> empty(LDH): <xsl:value-of select="...
• 
  Debbie Lockett Saxon-JS

  16:24 · Edited issue

  Selenium test `iss5036` added to our test suite (based on Martin's sample test). Bug #5036 (In Progress): key() doesn't work on ixsl:page() after ixsl:replace-content?

  Not sure it's the best subject, but this is what seems to be happening here (see the last 2 templates):
  https://namedgraph.github.io/saxon-js2-test/client.xsl
  Live demo: https://namedgraph.github.io/saxon-js2-test/
  Click the `[@CLA...
• 
  Debbie Lockett Martin is right that the key index is only built once, but since the HTML page is mutable this is not necessarily good enough. As Mike and Martin have noted, this restriction is unfortunately not documented. So in the short-term, we need...

  16:14 · Commented on issue

2021-07-06

• 
  Debbie Lockett Saxon-JS

  18:52 · Closed issue

  Closing this support issue with nothing to fix, as the user has worked out for themselves how to resolve the problem by adjusting the script and the way `SaxonJS.transform` is called. Support #5034 (Closed): Run multiple instances in parallel

  I just found and started using the Saxon-JS to be able to run Schematron validations on Peppol (Peppol.eu) messages and it works great!
  I've "pre-compiled" the Schemat's needed into JSON (using schxslt and xslt3) and I am then executing...