The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

iframe is like an embedded browser window. If the server returns an error status code then you will see the response inside the iframe, unlike with object which instead will fall back and show its contents. So object isn't really a replacement for iframe if you don't want the fallback mechanism.

object is like an autodetect element; it can act like an <img>, like an <iframe>, like an <applet>, like an <embed>, and it can even also be a form control. Given that there still is no interoperability between browsers on how to handle <object> after eight years shows that overloading one element to do many different things isn't the best thing to do.

iframe is like an embedded browser window. If the server returns an error status code then you will see the response inside the iframe, unlike with object which instead will fall back and show its contents. So object isn't really a replacement for iframe if you don't want the fallback mechanism.

object is like an autodetect element; it can act like an <img>, like an <iframe>, like an <applet>, like an <embed>, and it can even also be a form control. Given that there still is no interoperability between browsers on how to handle <object> after eight years shows that overloading one element to do many different things isn't the best thing to do.