Mason Freed
1f6242daf9
Automatic update from web-platform-tests Mark element-render-blocking-* slow These all contain multiple calls to generateParserDelay(), which is a ~1 second delay. Some (e.g. see crbug.com/452313201) are timing out. Mark them all potentially slow. Fixed: 452313201 Change-Id: I7b20daa182b47d6c36e319830bf77fd584960de9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7056574 Reviewed-by: Joey Arhar <jarhar@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1531912} -- wpt-commits: 5eb90e18588735ef382e7815233c6e3267a149cb wpt-pr: 55531
25 lines
754 B
HTML
25 lines
754 B
HTML
<!DOCTYPE html>
|
|
<meta name="timeout" content="long">
|
|
<head>
|
|
<script src="/resources/testharness.js"></script>
|
|
<script src="/resources/testharnessreport.js"></script>
|
|
<script src="support/utils.js"></script>
|
|
<title>link rel=expect: render blocking stops waiting when the document finishes loading</title>
|
|
|
|
<link rel=expect href="#invalid" blocking="render">
|
|
<script>
|
|
const startTime = performance.now();
|
|
|
|
async_test((t) => {
|
|
requestAnimationFrame(() => {
|
|
t.step(() => assert_less_than(performance.now() - startTime, 3000, "requestAnimationFrame should not have been delayed by the link that didn't find its target after load completes"));
|
|
t.done();
|
|
});
|
|
}, "");
|
|
</script>
|
|
</head>
|
|
<body>
|
|
<div id="first"></div>
|
|
<div id="last"></div>
|
|
</body>
|