Files
tubestation/testing/web-platform/tests/requestidlecallback/deadline-max.html
Noam Rosenthal 847e7dea2b Bug 1735042 [wpt PR 31177] - Tests for requestIdleCallback deadline computation, a=testonly
Automatic update from web-platform-tests
Tests for requestIdleCallback deadline computation (#31177)

* Tests for requestIdleCallback deadline computation

Deadline should be:
- capped at 50ms
- capped at 1000/60 (~16ms) when there is a pending rAF callback
- capped at the time of the next timeout
- be updated when the above conditions change, during the callback itself

See https://github.com/whatwg/html/pull/7166

Co-authored-by: Philip Jägenstedt <philip@foolip.org>
--

wpt-commits: 6ae31b2052754cb7645ba0e4c7c8ec43681d4a36
wpt-pr: 31177
2022-04-21 12:04:21 +00:00

21 lines
894 B
HTML

<!DOCTYPE html>
<title>window.requestIdleCallback max idle period deadline.</title>
<meta name="timeout" content="long">
<link rel="author" title="Noam Rosenthal" href="mailto:noam@webkit.org" />
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="resources/ric-utils.js"></script>
<script>
promise_test(async done => {
for (let i = 0; i < getRICRetryCount(); ++i)
assert_less_than_equal(await getDeadlineForNextIdleCallback(), 50)
}, 'Check that the deadline is less than 50ms.');
</script>
<h1>Test of requestIdleCallback deadline behavior</h1>
<p>This test validates that deadlines returned for requestIdleCallback are less than 50ms.</p>
<p>The test can pass accidentally as idle deadlines have a maximum but they can always be shorter.
It runs multiple times to expose potential failures.</p>
<div id="log"></div>