Sheriff: disable SitePerProcessWebViewTest.ContentScriptInOOPIF on Win

The test is flaky. Note that it is already disabled on Mac in a
different way, see crbug.com/1330015

Bug: 1363124
Change-Id: Ie14d0d5cdaabe580e1db39bfbcd5d8df63dc0502
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3902307
Auto-Submit: Elizabeth Popova <lizapopova@google.com>
Reviewed-by: Vidhan Jain <vidhanj@google.com>
Owners-Override: Elizabeth Popova <lizapopova@google.com>
Commit-Queue: Elizabeth Popova <lizapopova@google.com>
Cr-Commit-Position: refs/heads/main@{#1048571}
diff --git a/chrome/browser/apps/guest_view/web_view_browsertest.cc b/chrome/browser/apps/guest_view/web_view_browsertest.cc
index 4ed0e8a..caeae3d 100644
--- a/chrome/browser/apps/guest_view/web_view_browsertest.cc
+++ b/chrome/browser/apps/guest_view/web_view_browsertest.cc
@@ -6081,7 +6081,14 @@
 
 // Checks that content scripts work in an out-of-process iframe in a <webview>
 // tag.
-IN_PROC_BROWSER_TEST_F(SitePerProcessWebViewTest, ContentScriptInOOPIF) {
+// TODO(crbug.com/1363124): Fix flakiness on win10_chromium_x64_rel_ng. The test
+// is also disabled on mac11-arm64-rel using filter.
+#if BUILDFLAG(IS_WIN)
+#define MAYBE_ContentScriptInOOPIF DISABLED_ContentScriptInOOPIF
+#else
+#define MAYBE_ContentScriptInOOPIF ContentScriptInOOPIF
+#endif
+IN_PROC_BROWSER_TEST_F(SitePerProcessWebViewTest, MAYBE_ContentScriptInOOPIF) {
   ASSERT_TRUE(StartEmbeddedTestServer());
   // Load an app with a <webview> guest that starts at a data: URL.
   LoadAppWithGuest("web_view/simple");