- From: Mike West <notifications@github.com>
- Date: Mon, 07 Oct 2019 05:43:23 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 7 October 2019 12:43:45 UTC
> at that point it is navigation and cannot be used as a subresource anymore I hesitate to accept this claim. :) Per spec, you're probably right. But short of auditing Chromium's plugin loading code, I'm not sure that it's practically the case in that engine. The code is a big mess, and it's not clear to me that it couldn't backslide into having an effect on the document in which it's embedded. I really can't wait until we can lock most of the weirdness behind a PPAPI flag for enterprise. I'm willing to be convinced that `navigate` / `embed` is reasonable, but I think I'd like to err on the side of advertising the worst-case potential with `no-cors`. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/948#issuecomment-538991775
Received on Monday, 7 October 2019 12:43:45 UTC