- From: Mike West <notifications@github.com>
- Date: Mon, 07 Oct 2019 07:12:11 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 7 October 2019 14:12:32 UTC
> Wouldn't that end up affecting other parts of the system in weird ways? E.g., how a service worker is selected to handle the request? The way things are specified today, I'm not sure any of our current behaviors around this space are correct. :) What would you like the behavior to be for Service Workers? Could we treat `<embed>` navigations the same way we treat the original request from the `<embed>` element itself? cc @jakearchibald who possibly has opinions. > And is no-cors always worse than navigate? My assumption is that `no-cors` can/will end up in an attacker's memory, whereas a `navigate` probably won't (assuming out-of-process frames). @arturjanc probably has an opinion from the server side of things... -- 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-539031247
Received on Monday, 7 October 2019 14:12:32 UTC