Project

Profile

Help

Bug #3738

Cannot set properties to null using ixsl:set-property

Added by Debbie Lockett 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Sprint/Milestone:
-
Start date:
2018-04-06
Due date:
% Done:

100%

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

Description

It should be possible to use ixsl:set-property to set a property of a JS object to null, by supplying the empty sequence as the @select expression. However this is not allowed at compile time.

Issue initially raised in Feature #3569, but deserves separate bug.

Fixing the compile time problem then shows up a problem in the run time. There are different ways of representing the empty sequence internally. The internal convertToJS method does not work correctly when the item to be converted is null (as returned by Iter.Empty.next()). But note that an empty sequence represented internally as an empty array is converted to null correctly.

History

#1 Updated by Debbie Lockett 6 months ago

Saxon bug #3739 raised to track related compile time fix.

JS unit test ixsl/setProperty03 added (set nodeValue property of a text node to null).

#2 Updated by Debbie Lockett 6 months ago

  • Status changed from New to Resolved
  • Fix Committed on JS Branch 1.0, Trunk added

Fix committed on 1.x and trunk branches. (Use requires bug #3739 compile time fix)

#3 Updated by Debbie Lockett 5 months ago

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

Bug fix applied in the Saxon-JS 1.1.0 maintenance release.

Please register to edit this issue

Also available in: Atom PDF Tracking page