.then improperly propagates progress from locked-in Deferred #3062
|
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. |
|
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! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.