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

Yes -- before you mentioned the fact that `object` will resize based on image intrinsic dimensions I didn't realize that this is a web-observable difference between `iframe` and `object` and thought it should be safe to have `navigate` for a subsequent `object` navigation. Knowing this, I think at least from a security perspective the hybrid model isn't really useful and it would ideally be `no-cors` always.

That said, I think @mikewest is reasonably annoyed at me for unproductively griping here :) Practically, we can do all the things Mike mentioned above to reduce the likelihood of `navigate` for `object` being a problem. It has drawbacks, but it's *an* outcome, it's somewhat principled, and as long as browsers are consistent in what they do here, we'll be able to deal with it. So, uh, let's ship it?


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