Actions
Bug #3219
closed
IntersectExceptExprP pattern default priority calculated incorrectly
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2017-05-12
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.7
Fix Committed on Branch:
9.7, trunk
Fixed in Maintenance Release:
Platforms:
Description
https://www.w3.org/Bugs/Public/show_bug.cgi?id=30110 suggests that the XSLT test cases map-063 and map-064 make wrong assumptions about the default priority of intersect/except patterns. It appears that Saxon leaves default priority for ExceptPattern and IntersectPattern at +0.5 rather than propagating the priority of the first operand, and thus the (incorrect) tests have been passed incorrectly.
Updated by Michael Kay almost 7 years ago
- Status changed from New to Resolved
- Fix Committed on Branch 9.7, 9.8 added
Patch committed on the 9.7 and 9.8 branches.
Updated by O'Neil Delpratt almost 7 years ago
- Fix Committed on Branch trunk added
- Fix Committed on Branch deleted (
9.8)
Updated by O'Neil Delpratt almost 7 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.7.0.19 added
Bug fix applied in the 9.7.0.19 maintenance release.
Please register to edit this issue
Actions
.