- Email: email@example.com
- Registered on: 2014-03-13
- Last connection: 2019-05-23
Fix committed for 9.9 (and 10.0 dev) documentation.
Online 9.9 documentation updated (XML and HTML versions).
Bug #4224 (Resolved): Text about Xslt30Transformer uses wrong method name as asDestination(); met...http://saxonica.com/html/documentation/using-xsl/embedding/s9api-transformation.html says
> The Xslt30Transformer does not implement the Destination interface directly; but you can call its asDestination() method to get a Destination ...
Relatedly: referring to the Saxon-CE documentation, the design for `ixsl:set-attribute` was inspired by `xsl:attribute`: "The instruction has attributes name, namespace, and select, and works in exactly the same way as `xsl:attribute`, e... Feature #3572: Have an extra attribute for ixsl:set-attribute to select the element to be affectedIt would be nice if `<ixsl:set-attribute>` had an extra attribute so that it would not work on the current element, but on the element referenced by that attribute, much in the same way as the `object` attribute of `<ixsl:set-property>`....
Thanks for reporting this. It has been added to the list of things to fix in makeHttpRequest! Bug #4191: Saxon-JS error on null Content-TypeIn my UI, I poll the server and refresh content on the page that's changed. I added support for the etag header and ran across a Saxon-JS bug. When I sent an If-None-Match header and the resource is unchanged, the server sends back a ...
As Martin has suggested, I can confirm that the problem is not actually caused by `parse-xml()`. The result from `parse-xml()` does have the correct XHTML namespace (and html prefix).
Furthermore, the Saxon-JS special treatment of XHT... Bug #4176 (In Progress): parse-xml() in Saxon-JS loses html namespaceTo reproduce:
1. Unzip the attached zip file, saxon-js-parse-xml-bug.zip to a directory served up by a web server.
2. Also make Saxon-JS 1.2.0 available there
3. Edit test.html to adjust the path to Saxon-JS
4. Open the url to tes...
Thanks also for these additional comments. I will indeed look into making the appropriate changes to resolve these issues too! And do let us know if you come across anything else odd. General: RE: http-request error response bodies in Saxon-JS 1.2.0When I use ixsl:schedule-action to do an http-request, I'm not getting a body in the response map for errors (though the bodies do show up just fine for 2xx responses). For example, POSTing a malformed document, I'm returned:
Thanks for the repro.
Rather than wrapping everything in the xsl:try, I think you should put the xsl:try inside the xsl:variable, e.g. something like:
<xsl:variable name="decodedDocinfoXML" as="node()?">
<xsl:try selec... General: RE: Saxon-JS: xsl:result-document inside xsl:try failsMy UI can receive an xml document as a uri-encoded, base64 encoded string passed in through a query param. I decode it (using atob()) and then call parse-xml() on the string. Everything works fine UNLESS the string is garbage/not-xml. In...
Thanks for letting us know about the issue. Good to hear that you have found a work around! I will look into whether there is more we can do in Saxon-JS. General: RE: Saxon-JS: In Safari, 404 responses don't make it to the handlerHi there,
I'm doing an http-request of status-only="true" to see if a resource already exists or not and need to take different actions depending on the result. If the resource doesn't already exist, I know I'll get a 404. In Firefox,...
Excellent, glad to hear that gives you a work around, until we get a fix in a new release! General: RE: http-request error response bodies in Saxon-JS 1.2.0When I use ixsl:schedule-action to do an http-request, I'm not getting a body in the response map for errors (though the bodies do show up just fine for 2xx responses). For example, POSTing a malformed document, I'm returned:
Having looked in the Saxon-JS code (BrowserPlatform makeHttpRequest) it appears that we only add `response.body` in the response map if `!request["status-only"] && http.status < 400`. ...
Also available in: Atom