[WPT] ResourceTiming + cross-origin CSS + MemoryCache (#35279)
Because ResourceTiming processing goes through a different
code path in Chrome depending on whether subresources
are served by MemoryCache or not, this CL adds a
MemoryCache-served version of
no-entries-for-cross-origin-css-fetched-memory-cache.sub.html.
This is failing only on Chrome (both before and after
https://chromium-review.googlesource.com/c/chromium/src/+/3781346
while a little different failing reasons).
Bug: 532399
Change-Id: I0dc2ccd8789897c0e6086940552d865e96e3b0fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3793431
Reviewed-by: Noam Rosenthal <nrosenthal@chromium.org>
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1039520}
Co-authored-by: Hiroshige Hayashizaki <hiroshige@chromium.org>diff --git a/resource-timing/no-entries-for-cross-origin-css-fetched-memory-cache.sub.html b/resource-timing/no-entries-for-cross-origin-css-fetched-memory-cache.sub.html
new file mode 100644
index 0000000..2cfcfc7
--- /dev/null
+++ b/resource-timing/no-entries-for-cross-origin-css-fetched-memory-cache.sub.html
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML>
+<meta charset=utf-8>
+<title>Make sure that resources fetched by cross origin CSS are not in the timeline.</title>
+<script src="/resources/testharness.js"></script>
+<script src="/resources/testharnessreport.js"></script>
+<script src="/common/get-host-info.sub.js"></script>
+<body>
+<script>
+// This test is mostly the same as no-entries-for-cross-origin-css-fetched.html
+// but loads the subresources from another Document (<iframe>) earlier before
+// they are loaded via cross-origin CSSs, because the ResourceTiming processing
+// goes through a different code path in Chrome when served from MemoryCache
+// (`ResourceFetcher::DidLoadResourceFromMemoryCache`).
+function runTest() {
+ const link = document.createElement("LINK");
+ link.rel = "stylesheet";
+ link.id = "cross_origin_style";
+ link.href = "http://{{hosts[][www1]}}:{{ports[http][1]}}/resource-timing/resources/nested.css";
+ document.body.appendChild(link);
+}
+</script>
+<script>
+ const t = async_test("Make sure that resources fetched by cross origin CSS are not in the timeline.");
+ window.addEventListener("load", function() {
+ // A timeout is needed as entries are not guaranteed to be in the timeline before onload triggers.
+ t.step_timeout(function() {
+ const url = (new URL(document.getElementById("cross_origin_style").href));
+ const prefix = url.protocol + "//" + url.host;
+ assert_equals(performance.getEntriesByName(prefix + "/resource-timing/resources/resource_timing_test0.css?id=n1").length, 0, "Import should not be in timeline");
+ assert_equals(performance.getEntriesByName(prefix + "/fonts/Ahem.ttf?id=n1").length, 0, "Font should not be in timeline");
+ assert_equals(performance.getEntriesByName(prefix + "/resource-timing/resources/blue.png?id=n1").length, 0, "Image should not be in timeline");
+ t.done();
+ }, 200);
+ });
+</script>
+<iframe src="resources/no-entries-for-cross-origin-css-fetched-memory-cache-iframe.sub.html" onload="runTest()"></iframe>
+<ol>Some content</ol>
+</body>
diff --git a/resource-timing/resources/no-entries-for-cross-origin-css-fetched-memory-cache-iframe.sub.html b/resource-timing/resources/no-entries-for-cross-origin-css-fetched-memory-cache-iframe.sub.html
new file mode 100644
index 0000000..f479134
--- /dev/null
+++ b/resource-timing/resources/no-entries-for-cross-origin-css-fetched-memory-cache-iframe.sub.html
@@ -0,0 +1,8 @@
+<!DOCTYPE HTML>
+<html>
+<head>
+<link rel="stylesheet" href="http://{{hosts[][www1]}}:{{ports[http][1]}}/resource-timing/resources/nested.css">
+</head>
+<body>
+<ol>Some content</ol>
+</body>
