Bug 1378342 - AbortSignal/AbortController - part 7 - Fix a WPT related to AbortSignal and Fetch, r=bkelly

testing/web-platform/meta/fetch/api/abort/general.html.ini

@@ -7,9 +7,6 @@
   [Window: Signal removed by setting to null]
     expected: FAIL
 
-  [Window: Underlying connection is closed when aborting after receiving response - no-cors]
-    expected: FAIL
-
   [Window: Stream errors once aborted. Underlying connection closed.]
     expected: FAIL
 
@@ -31,9 +28,6 @@
   [DedicatedWorkerGlobalScope: Already aborted signal rejects immediately]
     expected: FAIL
 
-  [DedicatedWorkerGlobalScope: Underlying connection is closed when aborting after receiving response - no-cors]
-    expected: FAIL
-
   [DedicatedWorkerGlobalScope: Stream errors once aborted. Underlying connection closed.]
     expected: FAIL
 
@@ -55,9 +49,6 @@
   [SharedWorkerGlobalScope: Already aborted signal rejects immediately]
     expected: FAIL
 
-  [SharedWorkerGlobalScope: Underlying connection is closed when aborting after receiving response - no-cors]
-    expected: FAIL
-
   [SharedWorkerGlobalScope: Stream errors once aborted. Underlying connection closed.]
     expected: FAIL
 

testing/web-platform/tests/fetch/api/abort/general.js

@@ -309,7 +309,7 @@ promise_test(async t => {
     mode: 'no-cors'
   });
 
-  const stashTakeURL = new URL(`../resources/stash-take.py?key=${stateKey}`);
+  const stashTakeURL = new URL(`../resources/stash-take.py?key=${stateKey}`, location);
   stashTakeURL.hostname = 'www1.' + stashTakeURL.hostname;
 
   const beforeAbortResult = await fetch(stashTakeURL).then(r => r.json());