Bug 1638711 - Mark WPTs that incorrectly expect synchronous security checks as failing. r=asuth

Differential Revision: https://phabricator.services.mozilla.com/D77955

dom/clients/manager/ClientNavigateOpChild.cpp

@@ -266,6 +266,10 @@ RefPtr<ClientOpPromise> ClientNavigateOpChild::DoNavigate(
     /// the spec, but does match the current behavior of both us and Chrome.
     /// https://github.com/w3c/ServiceWorker/issues/1500 tracks sorting that
     /// out.
+    /// We now run security checks asynchronously, so these tests now
+    /// just fail to load rather than hitting this failure path. I've
+    /// marked them as failing for now until they get fixed to match the
+    /// spec.
     nsPrintfCString err("Invalid URL \"%s\"", aArgs.url().get());
     CopyableErrorResult result;
     result.ThrowTypeError(err);

testing/web-platform/meta/service-workers/service-worker/client-navigate.https.html.ini

@@ -30,6 +30,5 @@
       if os == "mac": ["PASS", "TIMEOUT", "NOTRUN"]
 
   [Navigating to mixed-content iframe should reject with TypeError]
-    expected:
-      if webrender and (os == "linux") and not debug and not fission: ["PASS", "TIMEOUT"]
+    expected: FAIL
 

testing/web-platform/meta/service-workers/service-worker/windowclient-navigate.https.html.ini

@@ -0,0 +1,3 @@
+[windowclient-navigate.https.html]
+  [invalid url (file:///) worker side]
+    expected: FAIL