Skip to content

Commit

Permalink
[resource-timing] Revamp buffer_full_when_shrink_buffer_size.html
Browse files Browse the repository at this point in the history
Bug: 1171767
Change-Id: I08ff6c59f18c339e98709a3c8262805477c2dce3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2964112
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Tom McKee <tommckee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#892675}
  • Loading branch information
Yoav Weiss authored and Chromium LUCI CQ committed Jun 15, 2021
1 parent 2928dcc commit 85cbd2c
Show file tree
Hide file tree
Showing 2 changed files with 29 additions and 31 deletions.
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
<!DOCTYPE HTML>
<html>
<head>
<meta charset="utf-8" />
<title>This test validates that reducing the buffer size after entries were
queued does not drop those entries, nor does it call the
resourcetimingbufferfull event callback.</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 fillUpTheBufferWithTwoResources();
performance.setResourceTimingBufferSize(1);
await waitForNextTask();
checkEntries(2);
}, "Test that if the buffer is reduced after entries were added to it, those" +
" entries don't get cleared, nor is the resourcetimingbufferfull event" +
" being called.");
</script>
</body>
</html>

This file was deleted.

0 comments on commit 85cbd2c

Please sign in to comment.