Re: [w3c/ServiceWorker] Create Service Worker from Blob/String that does not persist and auto claims for testing (Issue #1642)

asutherland left a comment (w3c/ServiceWorker#1642)

> Considering the high potential costs for both implementation and specification work, I am wondering about the use cases that would motivate vendors to undertake this. I am concerned that without a strong cost-benefit argument, adoption among vendors could be challenging.

I think an opinionated but fair take on the use-cases to be:
1. Get the effect of adding `onactivate = async () => { await clients.claim(); controller.unregister(); };` to a SW script without having to add that line.
2. Be able to bypass fundamental aspects of the ServiceWorker security model by providing the script as a Blob or String. 

From my perspective, this is a non-starter due to security concerns from the second point.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1642#issuecomment-2944781933
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1642/2944781933@github.com>