Actions
Bug #3870
closed
Mishandled "undefined" in code for filter expression
Start date:
2018-08-02
Due date:
% Done:
100%
Estimated time:
Applies to JS Branch:
1.0, Trunk
Fix Committed on JS Branch:
1.0, Trunk
Fixed in JS Release:
SEF Generated with:
Platforms:
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().
Updated by Debbie Lockett about 6 years ago
- Status changed from New to Resolved
- Fix Committed on JS Branch 1.0, Trunk added
Patch committed.
Updated by Debbie Lockett about 6 years 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
Actions
Also available in: Atom PDF Tracking page
.