Re: [whatwg/fetch] Aborting a fetch: The Next Generation (#447)

@benjamingr 
I understand. Regarding an XHR Polyfill, the difference is the amount of code required and performance. The iframe based solution offers no performance disadvantage and it enables performing fetch requests in a separate thread. It works with the original Fetch input and promise with no serialization/conversion overhead. It actually uses the original Fetch API in the iframe.

@Morantron 
It works with `frame-src 'none';`. Currently `script-src 'unsafe-inline'` is required but this will be solved in a upcoming update so that there are no CSP restrictions.

-- 
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/issues/447#issuecomment-316299306