-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): use setTimeout
when coalescing tasks in Node.js
#50820
Conversation
bfb1911
to
4ef1556
Compare
This commit updates the implementation of the `getNativeRequestAnimationFrame` and checks whether the current code runs in the browser before retrieving `requestAnimationFrame`. `requestAnimationFrame` is not available when the code is running in the Node.js environment. We have to fallback to `setTimeout` for delaying the change detection.
// cc @JiaLiPassion @alan-agius4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arturovt thanks for the fix! 👍
TGP. |
Caretaker note: the TGP is "green", this PR is ready for merge. |
This commit updates the implementation of the `getNativeRequestAnimationFrame` and checks whether the current code runs in the browser before retrieving `requestAnimationFrame`. `requestAnimationFrame` is not available when the code is running in the Node.js environment. We have to fallback to `setTimeout` for delaying the change detection. PR Close #50820
…#50820) This commit updates the implementation of the `getNativeRequestAnimationFrame` and checks whether the current code runs in the browser before retrieving `requestAnimationFrame`. `requestAnimationFrame` is not available when the code is running in the Node.js environment. We have to fallback to `setTimeout` for delaying the change detection. PR Close angular#50820
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…#50820) This commit updates the implementation of the `getNativeRequestAnimationFrame` and checks whether the current code runs in the browser before retrieving `requestAnimationFrame`. `requestAnimationFrame` is not available when the code is running in the Node.js environment. We have to fallback to `setTimeout` for delaying the change detection. PR Close angular#50820
…#50820) This commit updates the implementation of the `getNativeRequestAnimationFrame` and checks whether the current code runs in the browser before retrieving `requestAnimationFrame`. `requestAnimationFrame` is not available when the code is running in the Node.js environment. We have to fallback to `setTimeout` for delaying the change detection. PR Close angular#50820
This commit updates the implementation of the
getNativeRequestAnimationFrame
and checks whether the current code runs in the browser before retrievingrequestAnimationFrame
.requestAnimationFrame
is not available when the code is running in the Node.js environment. We have to fallback tosetTimeout
for delaying the change detection.closes: #50801