.then improperly propagates progress from locked-in Deferred #3062
Comments
|
We got an external report as well and as far as I understand it's a regression so I added the "Needs review" label as we might want that for 3.0.0. |
mgol
added a commit
to mgol/jquery
that referenced
this issue
Jun 8, 2016
Progress parameters are now correctly propagated from a deferred to which another deferred resolved unwrapping it. Thanks to @gibson042 for the report and a clear description of the problem and the needed fix. Fixes jquerygh-3062
4 tasks
|
PR: #3150. Please review, I want to get it in 3.0.0. And thanks @gibson042 for a clear description of the situation and the needed fix! |
mgol
added a commit
to mgol/jquery
that referenced
this issue
Jun 9, 2016
Progress parameters are now correctly propagated from a deferred to which another deferred resolved unwrapping it. Thanks to @gibson042 for the report and a clear description of the problem and the needed fix. Fixes jquerygh-3062 Closes jquerygh-3150
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When
.thenlocks in a Deferred by rebinding to a thenable resolved by its base, progress context is inappropriately propagated as progress data, and progress data is in appropriately wrapped in an array. It's probably easier to explain in code than in natural language: https://jsfiddle.net/zwavzvpx/ .This happens because
.notifyis used where.notifyWithbelongs, at deferred.js#L131.The text was updated successfully, but these errors were encountered: