FetchEvent should not forcibly reject an unresolved Promise when destructed

LayoutTests/http/tests/serviceworker/resources/fetch-event-test-worker.js

Index: LayoutTests/http/tests/serviceworker/resources/fetch-event-test-worker.js
diff --git a/LayoutTests/http/tests/serviceworker/resources/fetch-event-test-worker.js b/LayoutTests/http/tests/serviceworker/resources/fetch-event-test-worker.js
index 006d2acfe2a9bc3318f54d39ed4ccdaf9f46c210..8e906cbb6a9e9f1d04d588a224e1d9ab46e59c7e 100644
--- a/LayoutTests/http/tests/serviceworker/resources/fetch-event-test-worker.js
+++ b/LayoutTests/http/tests/serviceworker/resources/fetch-event-test-worker.js
@@ -20,10 +20,6 @@ function handleReject(event) {
     }));
 }
 
-function handleUnresolved(event) {
-    event.respondWith(new Promise(function(resolve, reject) { }));
-}
-
 function handleFetch(event) {
     event.respondWith(fetch('other.html'));
 }
@@ -37,7 +33,6 @@ self.addEventListener('fetch', function(event) {
         { pattern: '?ignore', fn: function() {} },
         { pattern: '?null', fn: handleNullBody },
         { pattern: '?reject', fn: handleReject },
-        { pattern: '?unresolved', fn: handleUnresolved },
         { pattern: '?fetch', fn: handleFetch }
     ];