Actions
Bug #5743
closedExpand text interacts badly with try/catch
Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2022-11-24
Due date:
% Done:
100%
Estimated time:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-
Description
This test:
<fred>
<xsl:try>
{error((), "BANG")}
<xsl:catch>
<xsl:sequence select="'CAUGHT'"/>
</xsl:catch>
</xsl:try>
</fred>
produces
<fred/>
where I think it should produce
<fred>CAUGHT</fred>
(As it does with SaxonJ).
Updated by Norm Tovey-Walsh about 1 year ago
This only occurs if the XX compiler is used
Updated by Norm Tovey-Walsh 4 months ago
In fact, it appears that the XX compiler does not process the text()
node children of xsl:try
. It's not directly related to expand-text at all. (Good one @Debbie)
Updated by Norm Tovey-Walsh 4 months ago
- Status changed from New to Resolved
Indeed, the problem was that text nodes that were direct children of xsl:try
were being lost.
Updated by Norm Tovey-Walsh 4 months ago
- Applies to JS Branch 2, Trunk added
- Fix Committed on JS Branch 2, Trunk added
Updated by Debbie Lockett about 1 month ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in JS Release set to SaxonJS 2.7
Bug fix applied in the SaxonJS 2.7 maintenance release.
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page