Re: [w3c/ServiceWorker] ServiceWorkerAutoPreload (PR #1756)

@yoshisatoyanagisawa commented on this pull request.



>        1. Else, resolve |preloadResponse| with undefined.
-      1. Let |fetchResult| be the result of [=Create Fetch Event and Dispatch=] with |request|, |registration|, |useHighResPerformanceTimers|, |timingInfo|, |workerRealm|, |reservedClient|, |preloadResponse|, and null.
+      1. Let |fetchResult| be the result of [=Create Fetch Event and Dispatch=] with |request|, |registration|, |useHighResPerformanceTimers|, |timingInfo|, |workerRealm|, |reservedClient|, |preloadResponse|, and |responseForAutoPreload|.

I feel you assume https://w3c.github.io/ServiceWorker/#create-fetch-event-and-dispatch-algorithm is handled in the renderer process.  I understand that the Chromium implementation is actually not.  Most of Step 17 is handled in the renderer process, but other steps in the algorithm would be handled in the browser process.

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

Message ID: <w3c/ServiceWorker/pull/1756/review/2941293772@github.com>