Closed thomheymann closed 11 years ago
This is expected behavior.
As specified, .then
issues another promise, rather than holding the reference to the original promise that it's chaining from. This is a breaking change from the jQuery implementation, and is documented in the readme for 0.4.0. Take a look at @domenic's explanation of this part of the promises A spec for the detailed reasoning behind this change.
Apologies for the confusion!
The library is mixing up promise states when filtering return values:
In browser using jQuery 1.8:
In node using underscore.deferred:
I'm on 0.4.0 installed via npm