#11776 closed bug (worksforme)
$.map is to eager on testing null
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Given
console.log($.map([ 1, undefined, , 2, null, 3 ], function (e, i) { return e; }));
results in
[ 1, 2, 3 ]
where I'd expect
[ 1, undefined, undefined, 2, 3 ]
Underlying problem is that we compare using value != null
instead of value !== null
Change History (3)
comment:1 Changed 11 years ago by
Keywords: | needsdocs added |
---|
comment:3 Changed 10 years ago by
Keywords: | needsdocs removed |
---|
Note: See
TracTickets for help on using
tickets.
I am sure there is code depending on
undefined
to remove the element by now, so I don't think we want to change the behavior. Instead I think we should document the current behavior.