File: buffer-full-eventually.html

package info (click to toggle)
firefox 145.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,653,344 kB
  • sloc: cpp: 7,594,932; javascript: 6,459,612; ansic: 3,752,905; python: 1,403,433; xml: 629,811; asm: 438,677; java: 186,421; sh: 67,287; makefile: 19,169; objc: 13,086; perl: 12,982; yacc: 4,583; cs: 3,846; pascal: 3,448; lex: 1,720; ruby: 1,003; exp: 762; php: 436; lisp: 258; awk: 247; sql: 66; sed: 54; csh: 10
file content (31 lines) | stat: -rw-r--r-- 964 bytes parent folder | download | duplicates (26) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
<!DOCTYPE HTML>
<html>
<head>
<meta charset="utf-8" />
<link rel="help"
      href="http://www.w3.org/TR/resource-timing/#performanceresourcetiming"/>
<title>This test validates that resource timing implementations have a finite
       number of entries in their buffer.</title>
<meta name="timeout" content="long">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
</head>
<body>
<script>
promise_test(t => {
  return new Promise(resolve => {
    let counter = 0;
    performance.onresourcetimingbufferfull = resolve;
    const loadImagesRecursively = () => {
      // Load an image.
      (new Image()).src = "resources/blue.png?" + counter;
      ++counter;
      // Yield to enable queueing an entry, then recursively load another image.
      t.step_timeout(loadImagesRecursively, 0);
    };
    loadImagesRecursively();
  });
}, "Finite resource timing entries buffer size");
</script>
</body>
</html>