summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/resource-timing/buffer-full-then-increased.html
blob: de517bf405c66e94e72f942de33ac6ab72807e2d (plain)
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
<!DOCTYPE HTML>
<html>
<head onload>
<meta charset="utf-8" />
<title>This test validates that synchronously adding entries in onresourcetimingbufferfull callback results in these entries being properly handled.</title>
<link rel="author" title="Google" href="http://www.google.com/" />
<link rel="help" href="https://www.w3.org/TR/resource-timing-2/#dom-performance-onresourcetimingbufferfull"/>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="resources/resource-loaders.js"></script>
<script src="resources/buffer-full-utilities.js"></script>
</head>
<body>
<script>
promise_test(async t => {
    addAssertUnreachedBufferFull(t);
    await fillUpTheBufferWithSingleResource();
    // These resources overflow the entry buffer, and go into the secondary buffer.
    load.xhr_sync(scriptResources[1]);
    load.xhr_sync(scriptResources[2]);
    // Immediately increase the size: the bufferfull event should not be fired.
    performance.setResourceTimingBufferSize(3);
    await waitForNextTask();
    checkEntries(3);
}, "Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event");
</script>
</body>
</html>