Re: [w3c/ServiceWorker] "no-cors" CSS SOP violation (#719)

noamr left a comment (w3c/ServiceWorker#719)

> 29\. This isn't really up to Fetch I think. CSS needs to define how it integrates with Fetch and avoid this SOP hole in the way Youenn suggests.

Given https://github.com/w3c/webappsec-csp/issues/828, perhaps fetch should accept something like a "muted" boolean that CSS would pass, that would resolve to skipping service workers, resource timing and CSP reporting?

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

Message ID: <w3c/ServiceWorker/issues/719/6635746700@github.com>