Project

Profile

Help

Bug #4768

closed

fn:transform(): source-node and global context item

Added by Michael Kay over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
XPath Conformance
Sprint/Milestone:
-
Start date:
2020-09-30
Due date:
% Done:

100%

Estimated time:
Applies to JS Branch:
2
Fix Committed on JS Branch:
2
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

The specification of fn:transform() states:

When source-node is supplied then the global-context-item (the context item for evaluating global variables) is the root of the tree containing the supplied node.

Test case fn-transform-82b in QT3 is failing; it appears that the global context item is set to the supplied value of source-node, not to the root of the containing tree.

Actions #1

Updated by Michael Kay over 3 years ago

Test fn-transform-82e is failing for the same reason (though it's not clear we should be running this test since it requires an XSLT 2.0 processor).

Actions #2

Updated by Michael Kay over 3 years ago

For transform-82e I think the results we produce should be allowed.

The test requests xslt-version:2.0, but the spec says:

If a processor that implements the requested XSLT version is available, then it is used.
Otherwise, if a processor that implements a version later than the requested version is available, then it is used.

So we're allowed to use an XSLT 3.0 processor; and if we do, then the global-context-item option will not be ignored as the test appears to expect.

However, if we make this change to the test, then Saxon/J 10.2 fails it.

Actions #3

Updated by Debbie Lockett over 3 years ago

  • Applies to JS Branch 2 added
Actions #6

Updated by Debbie Lockett about 3 years ago

  • Status changed from New to Resolved
  • Fix Committed on JS Branch 2 added

Marking resolved, as the tests are no longer failing.

Actions #7

Updated by Norm Tovey-Walsh about 3 years ago

  • Status changed from Resolved to Closed

This issue has been resolved in the Saxon 2.2 maintenance release.

Actions #8

Updated by Debbie Lockett about 3 years ago

  • % Done changed from 0 to 100
  • Fixed in JS Release set to Saxon-JS 2.2

Please register to edit this issue

Also available in: Atom PDF Tracking page