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

>They have quite different layout behavior in the image case, no? Including in Chrome. 

That's true, my claim earlier in the thread was incorrect: on testing again, I realize that Chrome has exactly the difference in behavior you're describing for `<embed src="[image URL]">` on the one hand, and direct navigating to an image from within a browsing context associated with `<embed src="[HTML URL]">`. I was testing the latter case, but not the former.

Still, both cases run through the same navigation architecture in Chrome, and we make a decision about whether to commit into a new browsing context vs. render the result.

I suspect that the cases in which the image-like display nature you're pointing to is something we could change if we wanted to simplify the model. Based on the same (sketchy because Canary) data source as above, <0.0001% of page views contain either `<embed>` or `<object>` used to render an image.

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