Actions
Bug #3861
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Incorrect type checking when xsl:key contains sequence constructor in place of @use attribute
Start date:
2018-07-28
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.8, trunk
Fix Committed on Branch:
9.8, trunk
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
Please register to edit this issue
Actions