[5.x] Avoid infinite digest loop caused by $watch and $timeout #10119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid infinite digest loop caused by $watch and $timeout
Backports PR #10036
Commit 1:
Avoid infinite digest loop in debounce
The custom debounce implementation uses Angular's
$timeout
, whichinteracts unfavourably with the unconditional
$watch
handler used inthe
fixed-scroll
directive. It results in an infinite digest beingtriggered about every 100ms. To avoid that, this commit uses the
invokeApply
option of$timeout
and instead calls$scope.$apply
conditionally.