Spec discussion: https://github.com/w3c/ServiceWorker/issues/1397Not needed because it's a simple modification to an existing feature. FetchEvent dispatched to a service worker is in a loading pipeline, which is performance sensitive. A new promise FetchEvent.handled is a promise to be resolved when a response is returned from a service worker to its client. This allows a service worker to explicitly wait to run some tasks until tasks critical to return a response to its client complete.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f81d329c-fd58-4a50-95f9-17e54cd1cfa3n%40chromium.org.
Thanks Ben and Alex.Now Ting is working on making a short explainer doc based on that comment and will send it out soon.Extracting that comment into a short doc might help. I'd specifically like to understand guarantees around ordering and potential for alleviating HOL-blocking behavior of post-handling cleanup work. E.g., in a cascade of fetch events, will this help us keep the SW more responsive to incoming fetches?
Sorry for the delay, I made an explainer for the FetchEvent.handled new API at https://github.com/tingshao/FetchEvent.handled
Please take a look when you have time. Any comment is welcome.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANr5HFWJ8pWq%3DYkuxkM%3D_mz9fWf96VD5g%3DWxR3EErwVcO2zRYA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEitt2-8EcYJb5xL94gPP0UEXXm1zucoHkv6ts60qU1m5Q%40mail.gmail.com.