Actions
Bug #4542
closedxsl:iterate/xsl:on-completion is not executed when processing a singleton
Start date:
2020-05-05
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
10, 9.9
Fix Committed on Branch:
10, 9.9
Description
Martin Honnen reports at https://saxonica.plan.io/boards/3/topics/7867?pn=1
Using Saxon 10 HE, the short test program
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="#all"
version="3.0">
<xsl:output method="xml" indent="yes" />
<xsl:template match="/" name="xsl:initial-template">
<xsl:iterate select="1">
<xsl:param name="p1" as="xs:string" select="'test'"/>
<xsl:on-completion>
<completion>
<xsl:copy-of select="$p1"/>
</completion>
</xsl:on-completion>
</xsl:iterate>
</xsl:template>
</xsl:stylesheet>
only outputs <?xml version="1.0" encoding="UTF-8"?>
. Shouldn't the xsl:on-completion
be executed and output e.g. <completion>test</completion>
?
Updated by Michael Kay over 4 years ago
Reproduced on 10.0 as W3C XSLT3 test case iterate-040.
Updated by Michael Kay over 4 years ago
- Category set to XSLT conformance
- Status changed from New to Resolved
- Priority changed from Low to Normal
- Applies to branch 10, 9.9 added
- Fix Committed on Branch 10, 9.9 added
Added further test iterate-041.
Fixed on the 9.9 and 10.9 branches.
Updated by O'Neil Delpratt over 4 years ago
- % Done changed from 0 to 100
- Fixed in Maintenance Release 10.1 added
Bug fix committed in the Saxon 10.1 maintenance release.
Updated by O'Neil Delpratt about 4 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 10.2, 9.9.1.8 added
- Fixed in Maintenance Release deleted (
10.1)
Bug fix applied on the Saxon 9.9.1.8 maintenance release.
Please register to edit this issue
Actions