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.

Sign up for GitHub

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

Jump to bottom

Suggestion: expose specific information instead of deadline #97

Open

noamr opened this issue Oct 26, 2021 · 1 comment

Labels

Contributor

noamr commented Oct 26, 2021

Deadline is computed by the following:

Is there rendering pending?
How long until a timer is about to expire?
How long has passed since the idle period started?
Did a new task make it into the global queue?

I'm suggesting that instead of computing the deadline based on this, we expose the different values, not necessarily from within the idle callback.

isFramePending, isInputPending etc.
Expose something about "when is the next timer about to expire"
Perhaps expose in the rIB when the idle period started

JS Libraries and websites can decide how they compute their "deadline".
The benefit is that this info is also valuable outside rIB.

Contributor

yoavweiss commented Oct 27, 2021

/cc @shaseley - who mentioned hearing this request from folks.

noamr added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment