I'd like to know if there is a known error in the way Saxon-JS handles CDATA containing elements.
I have a working XSLT 3.0 and XML process that includes taking text from a CDATA containing element and applying HTML markup in the transformation. I'll try asking the question without posting the script.
I'm using Saxon-HE 9.8.0.3 and trying the lasted Saxon-JS.
Everything converted from the .xsl files to the .sef files works except the expected format of the text taken from the CDATA containing element.
I have an element <docText> that only contains <![CDATA[ ... ]]> enclosed multiline text.
I call the template with something like:
<xsl:apply-templates select="ancestor::document/docText"/>
I match with <xsl:template match="docText/text()">
The final manipulation of the text in <docText> contained in a variable is output with the following:
<xsl:value-of select="$step9-2" disable-output-escaping="yes" />
Again, the output is correct with working HTML markup when I use the original transformation with Saxon-HE, XML and XSLT 3.0 from command line in Java. The transform script is almost identical for use with Saxon-JS and all the logic works except the formatting of the text originally in the CDATA sections. The text is output but as unformatted.
Is there any reason the error might be due to the way Saxon-JS does or doesn't handle CDATA sections the way Saxon-HE does?
Michael
See http://www.saxonica.com/saxon-js/documentation/index.html#!conformance/xslt30 saying
Saxon-JS does not implement the following optional features of the specification: schema-awareness, serialization, streaming, higher-order functions, and disable-output-escaping