Open Jamesernator opened 2 years ago
Although the symmetry is appealing, I think the current perspective is that "just yield" (at some target priority), is better than "conditionally yield" (but only if you think there is work with higher priority already queued).
The only difference would be if the overhead for the browser to "just yield" and resume is larger than the overhead to "see if it is worth yielding" and then not need to resume. But that is somewhat a premature optimization, that might be better solved directly by scheduler conventions.
(Note also that Chromium DevRel found enough negative examples of isInputPending
api that they stopped recommending it)
From other proposals we have
isFramePending
andisInputPending
however it would also be useful to have a more generalisTaskPending
which returnstrue
if any task of higher priority is scheduled to run. This would also include tasks created by the browser, i.e.isInputPending()
andisFramePending()
would both implyisTaskPending()
.The usage would be similar to
is{Input,Frame}Pending
: