Re: [whatwg/fetch] Split 'document' destination into 'frame' and 'iframe'. (#948)

The way the standard describes `<embed src>`/`<object data>` is roughly:

1. Let response be the result of fetching something.
2. If response is something that necessitates a browsing context, then:
   1. Create one.
   2. Navigate that browsing context to response.
3. Otherwise, display response without browsing context.

And then once there is a browsing context, you'd navigate that normally. It's surprising that Chrome has apparently a very different model from this. I haven't checked with folks familiar with Gecko's loading code recently, but I'm pretty sure the above is somewhat accurate for Gecko (now whether it's easy to get the right values might still be up for debate there of course).

-- 
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-543725116