Bug #3231
closedDefault treatment of Atomic items in text-only-copy incorrect
100%
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.
Updated by John Lumley over 7 years ago
- Status changed from New to Resolved
Patch applied to mode.js
- rev 6526
Updated by Debbie Lockett over 7 years ago
- Applies to JS Branch 1.0 added
- Fix Committed on JS Branch 1.0 added
Updated by Debbie Lockett over 7 years 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