Actions
Bug #2277
closedmatch="x/descendant::y[1]" gives spurious matches
Start date:
2015-01-04
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.6
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:
Platforms:
Description
See https://saxonica.plan.io/boards/3/topics/6051 from Martin Honnen.
Test case added as match-235 to W3C test suite.
Updated by Michael Kay almost 10 years ago
- Status changed from New to Resolved
A patch has been committed on the 9.6 and 9.7 branches.
Updated by Michael Kay almost 10 years ago
Further testing (match-238) reveals that the same coding error exists on another path, affecting patterns such as @a/descendant::b[2]@, where the positional filter is anything other than [1]. A further patch is being committed.
Updated by O'Neil Delpratt almost 10 years ago
- % Done changed from 0 to 100
- Fixed in version set to 9.6.0.4
Bug fix applied in the Saxon 9.6.0.4 maintenance release.
Updated by O'Neil Delpratt almost 10 years ago
- Status changed from Resolved to Closed
Updated by O'Neil Delpratt almost 9 years ago
- Sprint/Milestone set to 9.6.0.4
- Applies to branch 9.6 added
- Fix Committed on Branch 9.6 added
- Fixed in Maintenance Release 9.6.0.4 added
Updated by O'Neil Delpratt almost 9 years ago
- Sprint/Milestone changed from 9.6.0.4 to 9.6.0.3
- Fixed in Maintenance Release 9.6.0.3 added
- Fixed in Maintenance Release deleted (
9.6.0.4)
Updated by O'Neil Delpratt almost 9 years ago
- Sprint/Milestone changed from 9.6.0.3 to 9.6.0.4
- Fixed in Maintenance Release 9.6.0.4 added
- Fixed in Maintenance Release deleted (
9.6.0.3)
Please register to edit this issue
Actions