When deferred object is in a process of handing '.done' handers, if I attach another '.done' is it by intentional design that the new 'done' handler attached to a resolved object is handled last?

Here's the case...

// NORMAL CASE

var def = $.Deferred().resolve()

def.done(function() {

console.log("This line executes FIRST as expected.")

});

console.log("This line executes LAST as expected.");

IS THIS RIGHT? /

var def= $.Deferred();

setTimeout(function() {

def.resolve();

},300)

def.done(function() {

def.done(function() {

console.log("shouldn't this line come FIRST?")

})

console.log("shouldn't this line come LAST?")

})

Here's how this is relevant to a project I'm involved in. I need to ensure that a set of deferred objects, are all resolved at a certain point in the process. These objects can be resolved or reset (back to pending) at independent locations in the code. For this I use a convenient $.when construct. And to ensure that deferred objects are all resolved at that point I again, invoke the same $.when -- thus if all are resolved I expect '.done' to process immediately. Here's the mockup...

var test = function() {

var testAgain = false;

$.when(def1, def2, def3).done(function() {

if (testAgain) {

test();

return;

}

/ ALL RESOLVED CONTINUE WITH PROCESS. /

....

....

});

testAgain = true;

}

test();