Replacements
Although frames were included in the XHTML 1.0 specification, they were not carried across to XHTML 1.1. The intended eventual replacement is XFrames, which attempts to solve the problem of addressing a populated frameset through composite URIs. For those serving web content under the XHTML 1.0 specification, documents may be embedded within one another via either the object or iframe element tags. Under the 1.1 specification, iframe was removed, leaving only the object element for transclusion until browsers begin support for XFrames. Unfortunately, Internet Explorer 7 does not handle objects used to replace the function of an iframe, it doesn't recognize that a link from within the included page has the containing page as its _parent. Therefore constructing a menu to be included on every page, in imitation of a frameset, fails as the parent frame cannot be targeted. However most of the layout engines work perfectly well with this construct, some examples are: KHTML (Konqueror), WebKit (Safari and Google Chrome) and Gecko (Mozilla Firefox)
Frames become invalid in HTML5, with the exception that iframes remain.
Read more about this topic: Framing (World Wide Web)
Famous quotes containing the word replacements:
“The replacements are all like that. Not even old enough to carry a pack. All they know how to do is die.”
—Maxwell Anderson (1888–1959)