#3248 closed bug (fixed)
Simple solution to Array.prototype.call + jQuery.makeArray conflict
Reported by: | flesler | Owned by: | flesler |
---|---|---|---|
Priority: | major | Milestone: | 1.3 |
Component: | core | Version: | 1.2.6 |
Keywords: | Cc: | john, brandon, joern, davidserduke | |
Blocked by: | Blocking: |
Description
This is a possible fix to this annoying conflict.
Attachments (1)
Change History (5)
Changed 15 years ago by
Attachment: | makeArray[5824].diff added |
---|
comment:1 Changed 15 years ago by
Status: | new → assigned |
---|
comment:2 Changed 15 years ago by
comment:3 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
John approves :) Applied at [5825].
comment:4 Changed 14 years ago by
Now that isFunction is much shorter and faster, re added support for functions on [5915].
Note: See
TracTickets for help on using
tickets.
This will remove support for functions (regexps still supported) on makeArray. This passes all the tests on IE6, FF2, Opera 9.2, Opera 9.5, Safari 3. I assume the rest will follow.
I don't think it'll be an issue to drop this support as functions sent to the jQuery constructor are intercepted by init().
Shall I ?