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

> Very interesting, but there's no initial about:blank it seems, so there's no exposed browsing context (e.g., via self[0]) until the load event fires, as far as I can tell. So it's still a bit different from how iframe works, but much less so than in Firefox.

I think that's correct. If/when we actually get rid of plugins, it might be reasonable to make `embed` and `object` work more like strangely-spelled `iframe` elements? Given their usage in the wild, I think it's going to be hard to make substantial changes to their behavior.

Implementation details to the side, does the behavior in https://github.com/whatwg/fetch/pull/948#issuecomment-543560997 seem reasonable to you? If so, I'll figure out how to make it work in HTML and Chromium.

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

Received on Tuesday, 22 October 2019 12:50:59 UTC