Ticket #10331 (closed enhancement: invalid)
resolveWith error
| Reported by: | gabrielandresbrancolini@… | Owned by: | gabrielandresbrancolini@… |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | deferred | Version: | 1.6.4 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
Hi, I have an undefined error with resolveWith. I am using Asp.net 2.0 with datagrid and a datatable jquery plugin. What Ive done was this fix. Just want to share.
Best Regards,
Gabriel Andrés Brancolini
resolveWith: function(context, args) { Fix by everis software factory. if (
!(cancelled == undefined ? true : cancelled) && !(fired == undefined ? false : fired) && !(firing == undefined ? false : firing)
) {
make sure args are available (#8421)
args = args []; firing = 1; try {
Fix by everis software factory. if (callbacks.length != 0) {
while (callbacks[0]) {
callbacks.shift().apply(context, args); }
}
} finally {
fired = [context, args]; firing = 0;
}
} return this;
}
Change History
comment:1 Changed 20 months ago by timmywil
- Owner set to gabrielandresbrancolini@…
- Priority changed from undecided to low
- Status changed from new to pending
- Component changed from unfiled to deferred
comment:2 Changed 20 months ago by trac-o-bot
- Status changed from pending to closed
- Resolution set to invalid
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.
Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/FrKyN/ Open the link and click to "Fork" (in the top menu) to get started.