jQuery.map( array_like ) and bounding values

[Robert Katić]

Test: ​http://jsfiddle.net/YWeDX/

[Robert Katić]

Updated test: ​http://jsfiddle.net/CPj3F/

Previous one is not completely correct.

[timmywil]

Further discussion of this issue should be in the forums. The meaning of array-like is under scrutiny and this will probably result in a change in the docs. However, it is true that { length: 0 } is not supported, so the resolution of this bug's duplicate is accurate.

[timmywil]

Duplicate of #9023.

[Robert Katić]

True that all those bugs are related to what array-like is, but I would be careful to say this is an duplicate. It reports an different symptom.

[Robert Katić]

Not duplicate. #9023 was fixed for me, but this bug is not:

Patch: ​https://github.com/jquery/jquery/pull/368

[Robert Katić]

This would also fix #9750.

[addyosmani]

Reopening as it would appear that #9750 is a dupe and this already has a pull request on it.

[addyosmani]

#9750 is a duplicate of this ticket.

[ajpiano]

The consensus we've reached at this stime is that we will not be attempting to detect host objects in $.isPlainObject and $.map. While edge cases like this do come up, detection is unreliable and comes at a relatively high cognitive cost without clear benefit to the vast majority of jQuery users. If in the future, it becomes apparent that this issue is something that is a pain point to a larger contingent of developers, we can revisit the issue. We'll be documenting that array-like objects need to be converted into real arrays before being passed to $.map.

[Robert Katić]

@ajpiano: With your comment I have a serous suspicion that you really tried to understand what this bug/patch is about (certainly it is not about host objects). I don't blame you, it is probably my fault too (will try to be more obvious in future).

[ajpiano]

@rkatic: I hava serious suspicion you really meant to say that I "didn't" really try to understand what this bug/patch is about :) I read my own comment over though a bit and admit that it seems like a response to a different/multiple tickets - which is what I was attempting to do - to explain that at the recent triage sprint we've decided that the resolution to a number of these issues with handling edge cases in core methods will have documentation-, not code-, based solutions.

[addyosmani]

The docs for this item have been updated by Karl and I.