Actions
Bug #3219
closedIntersectExceptExprP 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.
Please register to edit this issue
Actions