Bug #3861
closed
Incorrect type checking when xsl:key contains sequence constructor in place of @use attribute
100%
Description
When the use expression of an xsl:key is computed using a sequence constructor rather than an XPath expression in an @use attribute, incorrect type checking is applied: the required type of the result is set to xs:anyAtomicType? rather than xs:anyAtomicType*, disallowing a sequence of more than one value. (This applies whether or not composite="yes" is specified).
Test case key-097 added to the XSLT 3.0 test suite.
Raised by Martin Honnen here: https://saxonica.plan.io/boards/3/topics/7274
Updated by Michael Kay almost 6 years ago
- Status changed from New to Resolved
- Fix Committed on Branch 9.8, trunk added
It looks as if (before going on vacation) I fixed this for the development branch but not for 9.8.
Now fixed also for 9.8.
Updated by O'Neil Delpratt over 5 years ago
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.9.0.1 added
Bug fix applied in the Saxon 9.9.0.1 major release.
Leave open until fix applied in the next Saxon 9.8 maintenance release.
Updated by O'Neil Delpratt over 5 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 9.8.0.15 added
Bug fix applied in the Saxon 9.8.0.15 maintenance release.
Please register to edit this issue
.