Project

Profile

Help

Bug #3870

Mishandled "undefined" in code for filter expression

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

Status:
Closed
Priority:
Low
Sprint/Milestone:
-
Start date:
2018-08-02
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

When filtering an iterator for an array, if the predicate is out of range (at run time) then this is not handled correctly. i.e. when input.expand()[subscript - 1] returns undefined, we get an error. null rather than undefined should be supplied to Iter.Singleton().

History

#1 Updated by Debbie Lockett 8 months ago

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

Patch committed.

#2 Updated by Debbie Lockett 6 months ago

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

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

Please register to edit this issue

Also available in: Atom PDF Tracking page