Project

Profile

Help

Bug #3231

Default treatment of Atomic items in text-only-copy incorrect

Added by John Lumley about 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Sprint/Milestone:
-
Start date:
2017-05-22
Due date:
% Done:

100%

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

Description

For non-node items, the built-in text-only-copy rules currently return an iterator to the item. For atomic values this should involve a cast to a text node, as detailed in https://www.w3.org/TR/xslt-30/#built-in-templates-text-only-copy.

Note that this error may have 'corrected' errors in dealing with text-nodes in Expr.makeComplexContent() as raised in https://saxonica.plan.io/issues/3139, so some XSLT tests (such as next-match-027) may have passed due to a 'double-negative'. This will be investigated.

History

#1 Updated by John Lumley about 1 year ago

  • Status changed from New to Resolved

Patch applied to mode.js - rev 6526

#2 Updated by Debbie Lockett 10 months ago

  • Applies to JS Branch 1.0 added
  • Fix Committed on JS Branch 1.0 added

#3 Updated by Debbie Lockett 10 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in JS Release set to Saxon-JS 1.0.1

Bug fix applied in Saxon-JS 1.0.1 maintenance release.

Please register to edit this issue

Also available in: Atom PDF Tracking page