Project

Profile

Help

Bug #4793

xsl:copy-of with copy-namespaces="no" not working

Added by Michael Kay 11 months ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2020-10-10
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
10, 9.9, trunk
Fix Committed on Branch:
10, 9.9, trunk
Fixed in Maintenance Release:

Description

In response to a message from Martin Honnen, XSLT3 test case copy-5101 has been created which shows xsl:copy-of with copy-namespaces="no" not working.

https://saxonica.plan.io/boards/3/topics/8011?pn=1

The specific circumstances are that Saxon creates a virtual copy of the original, a wrapper whose methods should reflect the differences from the original including the absence of namespaces. But the NodeInfo.copy() method on the virtual copy (which is invoked by the serialize() function to send the node to a serializer) is simply copying the original, unchanged.

History

#1 Updated by Michael Kay 11 months ago

  • Status changed from New to In Progress

Fixed by adding to VirtualCopy.copy():

        if (dropNamespaces) {
            copyOptions &= ~CopyOptions.ALL_NAMESPACES;
        }

Needs regression testing.

#2 Updated by Michael Kay 11 months ago

  • Category set to XSLT conformance
  • Status changed from In Progress to Resolved
  • Priority changed from Low to Normal
  • Applies to branch 10, trunk added
  • Fix Committed on Branch 10, trunk added

Fix committed

#3 Updated by Michael Kay 11 months ago

  • Applies to branch 9.9 added
  • Fix Committed on Branch 9.9 added

I've also committed the patch for 9.9.

#4 Updated by O'Neil Delpratt 11 months ago

  • Fixed in Maintenance Release 9.9.1.8 added

Bug fix applied on the Saxon 9.9.1.8 maintenance release. Leaving open until applied on the Saxon 10 maintenance release.

#5 Updated by O'Neil Delpratt 11 months ago

Bug fix applied in the Saxon 10.3 maintenance release

#6 Updated by O'Neil Delpratt 11 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.3 added

Please register to edit this issue

Also available in: Atom PDF