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

I spent a couple days working on this,  but it turned out to be more complex than I had time for.  The issue I ran into is that chrome does not initiate the loads for things like background images, etc, until they are used by a style flush.  This is quite a bit after the sheet was loaded and parsed, so none of the tainting information is available.  That information would have to be plumbed though.  It was a bit too much for me since I'm not familiar with chrome's style system.

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