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

> Overall, I like the model of having initial loads via `embed`/`object` be `no-cors`, but turn into `navigate` when the browsing context gets navigated.

@annevk I think you would be happy with this too, given your comments in https://github.com/whatwg/fetch/pull/948#discussion_r331992431. Is that still your preference?

I don't think this distinction will be easy to implement in Chromium, given the way `<embed>`/`<object>` are intertwined with navigation code, but I'm happy to assume that it's possible, spec and test it accordingly, and move on to more interesting debates. :)

---

For clarity, I think we're saying that the initial request from `<embed>` would send:

```
Sec-Fetch-Dest: embed
Sec-Fetch-Mode: no-cors
Sec-Fetch-Site: whatever
```

and subsequent requests from `<embed>` caused either by internal interaction or by poking at `window.frames` would send:

```
Sec-Fetch-Dest: embed
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: whatever
```

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