Re: [w3c/ServiceWorker] Isolate fix for race-network-and-fetch-handler stall from PR #1764 (PR #1777)

@sisidovski commented on this pull request.



> @@ -3279,7 +3282,14 @@ spec: storage; urlPrefix: https://storage.spec.whatwg.org/
                       1. If |fetchHandlerResponse| is not null and not a [=network error=], and |raceFetchController| is not null, [=fetch controller/abort=] |raceFetchController|.
                       1. Let |raceFetchHandlerResult| be a [=race result=] whose [=race result/routed response=] is |fetchHandlerResponse| and [=race result/used route=] is {{RouterSourceEnum/"fetch-event"}}.
                       1. [=queue/Enqueue=] |raceFetchHandlerResult| to |queue|.

I still don't fully understand why none of responses may not be enqueued under the current spec. This line enqueues `raceFetchHandlerResult` without any conditions, so I expect at least the fetch handler result is enqueued, am I misunderstanding?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/pull/1777#pullrequestreview-2915517006
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/pull/1777/review/2915517006@github.com>