Skip to main content

Bug Tracker

Side navigation

#11477 closed bug (invalid)

Opened March 15, 2012 09:48PM UTC

Closed March 30, 2012 08:27AM UTC

A resolved/rejected $.Deferred does not trigger new handlers when attached in IE8

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.7.1
Keywords: Cc:
Blocked by: Blocking:

Code sample:

(new $.Deferred())
	.done(function (msg) {

I would expect an immediately resolved/reject deferred to immediately trigger any newly attached handlers as appropriate, and this is the case in Firefox, Chrome, and IE9. It's not happening in IE8 and below, however.

I'm going to be diving in to fix this myself, as it's for a project with a fairly tight deadline. Just thought you guys should be apprised of it as well.

Attachments (0)
Change History (2)

Changed March 15, 2012 10:17PM UTC by sindresorhus comment:1

owner: →
status: newpending

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: Open the link and click to "Fork" (in the top menu) to get started.

Changed March 30, 2012 08:27AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

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!