Debbie Lockett
- Login: deblock
- Email: debbie@saxonica.com
- Registered on: 2014-03-13
- Last connection: 2024-07-26
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 2 | 306 | 308 |
Reported issues | 6 | 151 | 157 |
Projects
Project | Roles | Registered on |
---|---|---|
Saxon | Manager, Developer, Reporter | 2014-04-04 |
Saxon-CE | Reporter | 2014-04-04 |
SaxonC | Manager, Developer, Reporter | 2014-04-04 |
SaxonJS | Manager, Developer, Reporter | 2016-08-11 |
SaxonMirrorHE | Manager, Developer | 2021-02-02 |
Activity
2024-07-19
-
Re #note-1: I've belated fixed the typos (on `saxonjs2` and `main`); and pushed the changes to the SaxonJS 2 documentation online. Bug #5678: Returning only the unconverted error object is burdonsome[We say](https://www.saxonica.com/saxon-js/documentation2/index.html#!api/transform/error-handling) that the third argument to `fn:error()` is returned "unconverted".
That's pretty inconvenient for users. I think we should return a co... -
For SaxonJS 3, a number of improvements have been made to make it easier for users to work directly with JavaScript objects inside XSLT, and avoid the usual SaxonJS type conversions between JavaScript and XDM.
The new IXSL functions `... Bug #5656 (Resolved): XDM array is not converted to a true JS array?According to [XDM to JavaScript Conversion](https://www.saxonica.com/saxon-js/documentation2/index.html#!xdm/conversions) `array(*)` should be converted to a JS array.
However this code:
```
<xsl:variable name="array" select="[ 'a' ... -
The new function `ixsl:json-parse()` is added in SaxonJS 3, which enables users to create JavaScript objects from JSON, without converting the result to XDM. This makes it possible to do:
``` xml
<xsl:variable name="json-string" as="... Bug #4815 (Resolved): Conversion of XDM maps to JS objectsOn 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...
2024-07-18
-
`ixsl:new()` will be available in SaxonJS 3. Feature #5057 (Resolved): Constructing JS objectsHi. I cannot seem to find a native way to construct JS objects, which makes porting JS code to XSLT complicated. It think it was possible with Saxon-CE, but I might be wrong.
I know there is `ixsl:eval()`, but since it accepts string ... -
The support for promises in SaxonJS 3 will include `ixsl:all()` (and other corresponding functions for concurrency). Feature #5596 (Resolved): IXSL construct for Promises.all[`Promises.all](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all) is very useful when executing multipe promises at the same time:
> The `Promise.all()` method takes an iterable of promises as...
2024-07-03
-
Belatedly marking closed - the bug fix was applied in the Saxon 11.6 maintenance release. Bug #5886 (Closed): Serializer of s9api in Saxon 11 for json and adaptive output method seems to close underlying stream while that doesn't happen for output method xmlBased on my findings in https://saxonica.plan.io/boards/3/topics/9295 and what I fill explain further it appears Saxon 11 has a bug where the use of an s9api `Serializer` over an `OutputStream` as the `Destination` of an `Xslt30Transform...
-
Belatedly marking as closed - the bug fix was applied in the Saxon 12.4 Maintenance release. Bug #6152 (Closed): XML Reader seems to be reused instead of re-creatingUsing Saxon 12.3 I'm using the document() function in my XSLT like:
```
<xsl:message><xsl:value-of select="document('doctypeDitaTopic5.dita')"/></xsl:message>
```
In the Java code I set :
```
configuration.setParseOptions(confi... -
Marking closed - the change was made in the Saxon 12 documentation online a while ago. Feature #6030 (Closed): in xsl:next-match documentation topic, mention that non-tunneling parameters are not automatically propagated to the next-matching templateSection [6.8 Overriding Template Rules](https://www.w3.org/TR/xslt-30/#element-next-match) of the XSLT 3.0 spec states the following about how parameters are passed to the next-matching template:
> If a matching template rule R is fou... -
-
Support #5601 (Closed): Latter defined entity is honored rather than former one in Saxon-PE 11.3I'm testing Saxon-PE 10.8 and 11.3 for user project. When I convert XML file with entity reference, the former entity definition is not honored and the latter defined entity is honored in Saxon-PE 11.3.
I attached the sample file arch...
Also available in: Atom