Deferred: Deprecate setTimeout() usage under latest browsers. #5114
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.
Summary
Hi there, as you may know, Chrome/ium has been lately aggressively throttling background tabs, this may result in those setTimeout()-based promises/deferreds to never resolve until the tab becomes active again.
This PR is an attempt to prevent that, by using queueMicrotask under browsers supporting it. Also, the logic has been changed to dispatch those processes in bulk instead of individually, since the main reason for that throttling seems to be by having too many concurrent setTimeout()s running.
This implements a new
jQuery.asap()
function that will use eitherqueueMicrotask
orsetTimeout
for older browsers.I've observed that around this whole codebase there are several other uses of that
window.setTimeout( func )
pattern so perhaps I should move thisjQuery.asap()
elsewhere to be used in place of those as well (as part of another PR) ?Thanks!
Checklist