-
Notifications
You must be signed in to change notification settings - Fork 49.2k
Polyfill requestIdleCallback when native is not available #8833
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,149 @@ | ||
/** | ||
* Copyright 2013-present, Facebook, Inc. | ||
* All rights reserved. | ||
* | ||
* This source code is licensed under the BSD-style license found in the | ||
* LICENSE file in the root directory of this source tree. An additional grant | ||
* of patent rights can be found in the PATENTS file in the same directory. | ||
* | ||
* @providesModule ReactDOMFrameScheduling | ||
* @flow | ||
*/ | ||
|
||
'use strict'; | ||
|
||
// This a built-in polyfill for requestIdleCallback. It works by scheduling | ||
// a requestAnimationFrame, store the time for the start of the frame, then | ||
// schedule a postMessage which gets scheduled after paint. Within the | ||
// postMessage handler do as much work as possible until time + frame rate. | ||
// By separating the idle call into a separate event tick we ensure that | ||
// layout, paint and other browser work is counted against the available time. | ||
// The frame rate is dynamically adjusted. | ||
|
||
import type { Deadline } from 'ReactFiberReconciler'; | ||
|
||
var invariant = require('invariant'); | ||
|
||
// TODO: There's no way to cancel these, because Fiber doesn't atm. | ||
let rAF : (callback : (time : number) => void) => number; | ||
let rIC : (callback : (deadline : Deadline) => void) => number; | ||
if (typeof requestAnimationFrame !== 'function') { | ||
invariant( | ||
false, | ||
'React depends on requestAnimationFrame. Make sure that you load a ' + | ||
'polyfill in older browsers.' | ||
); | ||
} else if (typeof requestIdleCallback !== 'function') { | ||
// Wrap requestAnimationFrame and polyfill requestIdleCallback. | ||
|
||
var scheduledRAFCallback = null; | ||
var scheduledRICCallback = null; | ||
|
||
var isIdleScheduled = false; | ||
var isAnimationFrameScheduled = false; | ||
|
||
var frameDeadline = 0; | ||
// We start out assuming that we run at 30fps but then the heuristic tracking | ||
// will adjust this value to a faster fps if we get more frequent animation | ||
// frames. | ||
var previousFrameTime = 33; | ||
var activeFrameTime = 33; | ||
|
||
var frameDeadlineObject = { | ||
timeRemaining: ( | ||
typeof performance === 'object' && | ||
typeof performance.now === 'function' ? function() { | ||
// We assume that if we have a performance timer that the rAF callback | ||
// gets a performance timer value. Not sure if this is always true. | ||
return frameDeadline - performance.now(); | ||
} : function() { | ||
// As a fallback we use Date.now. | ||
return frameDeadline - Date.now(); | ||
} | ||
), | ||
}; | ||
|
||
// We use the postMessage trick to defer idle work until after the repaint. | ||
var messageKey = | ||
'__reactIdleCallback$' + Math.random().toString(36).slice(2); | ||
var idleTick = function(event) { | ||
if (event.source !== window || event.data !== messageKey) { | ||
return; | ||
} | ||
isIdleScheduled = false; | ||
var callback = scheduledRICCallback; | ||
scheduledRICCallback = null; | ||
if (callback) { | ||
callback(frameDeadlineObject); | ||
} | ||
}; | ||
// Assumes that we have addEventListener in this environment. Might need | ||
// something better for old IE. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. IE9+ supports |
||
window.addEventListener('message', idleTick, false); | ||
|
||
var animationTick = function(rafTime) { | ||
isAnimationFrameScheduled = false; | ||
var nextFrameTime = rafTime - frameDeadline + activeFrameTime; | ||
if (nextFrameTime < activeFrameTime && previousFrameTime < activeFrameTime) { | ||
if (nextFrameTime < 8) { | ||
// Defensive coding. We don't support higher frame rates than 120hz. | ||
// If we get lower than that, it is probably a bug. | ||
nextFrameTime = 8; | ||
} | ||
// If one frame goes long, then the next one can be short to catch up. | ||
// If two frames are short in a row, then that's an indication that we | ||
// actually have a higher frame rate than what we're currently optimizing. | ||
// We adjust our heuristic dynamically accordingly. For example, if we're | ||
// running on 120hz display or 90hz VR display. | ||
// Take the max of the two in case one of them was an anomaly due to | ||
// missed frame deadlines. | ||
activeFrameTime = nextFrameTime < previousFrameTime ? | ||
previousFrameTime : nextFrameTime; | ||
} else { | ||
previousFrameTime = nextFrameTime; | ||
} | ||
frameDeadline = rafTime + activeFrameTime; | ||
if (!isIdleScheduled) { | ||
isIdleScheduled = true; | ||
window.postMessage(messageKey, '*'); | ||
} | ||
var callback = scheduledRAFCallback; | ||
scheduledRAFCallback = null; | ||
if (callback) { | ||
callback(rafTime); | ||
} | ||
}; | ||
|
||
rAF = function(callback : (time : number) => void) : number { | ||
// This assumes that we only schedule one callback at a time because that's | ||
// how Fiber uses it. | ||
scheduledRAFCallback = callback; | ||
if (!isAnimationFrameScheduled) { | ||
// If rIC didn't already schedule one, we need to schedule a frame. | ||
isAnimationFrameScheduled = true; | ||
requestAnimationFrame(animationTick); | ||
} | ||
return 0; | ||
}; | ||
|
||
rIC = function(callback : (deadline : Deadline) => void) : number { | ||
// This assumes that we only schedule one callback at a time because that's | ||
// how Fiber uses it. | ||
scheduledRICCallback = callback; | ||
if (!isAnimationFrameScheduled) { | ||
// If rAF didn't already schedule one, we need to schedule a frame. | ||
// TODO: If this rAF doesn't materialize because the browser throttles, we | ||
// might want to still have setTimeout trigger rIC as a backup to ensure | ||
// that we keep performing work. | ||
isAnimationFrameScheduled = true; | ||
requestAnimationFrame(animationTick); | ||
} | ||
return 0; | ||
}; | ||
} else { | ||
rAF = requestAnimationFrame; | ||
rIC = requestIdleCallback; | ||
} | ||
|
||
exports.rAF = rAF; | ||
exports.rIC = rIC; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Thinking out loud:
performance.now()
andDate.now()
return very different values but they're being used interchangeably, driven by the param passed torequestAnimationFrame
. Wouldn't this cause problems if we ever end up mixing the 2 due to polyfills? (requestAnimationFrame
is supposed to be passed a time fromperformance.now()
but some polyfills areDate
based.)Fortunately I don't think this is likely to occur. It seems both are supported by everything we target except for:
Date.now
for both.requestAnimationFrame
but notperformance.now
. This version is 2.5 years old though and iOS has pretty strong upgrade adoption, so maybe we can just ignore this one point release.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.
If iOS 8.4 supports
requestAnimationFrame
but notperformance.now
my hypothesis is that the value passed torequestAnimationFrame
is the oldDate.now
version ofrequestAnimationFrame
.Yes, it is very possible that there is a browser that implements the new
requestAnimationFrame
without implementingperformance.now
. Seems unlikely though.However, even more likely is that there are browsers out there that implement the old
requestAnimationFrame
while already implementingperformance.now
. That's very possible.We could probably do a guess based on the value passed to
requestAnimationFrame
which one it is (if it is a very low number) and then switch dynamically between the two. For the case where the new rAF is implemented but noperformance.now
we could use aDate.now
time stamp instead. I'd rather not complicate it unless we know of at least one browser where either of this happens though. Perhaps we can call on the community to help out identifying issues here?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.
Hm. Actually I wonder if
performance.now
might be implemented behindperformance.webkitNow
in some cases which would trigger the bad case.