The following lines were added (+) and removed (-):
Newer browsers also allow the '''<iframe>''' tag to define an inline frame. The same rules forFirst introduced by Microsoft Internet Explorer in 1997, standardized in HTML 4.0 Transitional, allowed in HTML5. Modern browsers allow the '''<iframe>''' tag to define an inline frame. The same rules for== HTML5 Does Away with Frames, Mostly ==The <frameset> tag and all of it’s associated tags will not be coming back in HTML 5. The frame and frameset elements are not deprecated in HTML5, they have been designated obsolete. Semantics? By being declared obsolete in HTML5 standard it is said the elements are not to be used by Web developers. User agents will still have to support them and various sections in HTML. In the case of frame, frameset, and noframes they are designated as elements not in HTML because using them damages usability and accessibility - all according to the web standard nerds that think they know best. For more details see [http://www.w3.org/TR/html5-diff/#obsolete-elements HTML5 Obsolete Elements].the iframe element is still included in HTML5 because frame and frameset elements are not the same thing as the iframe. They do not result in the same product. *The frameset element replaces the body element in pages as a means to include a different document model for web pages: they are problematic for usability and accessibility. They break web browser bookmarking. Now what the original purpose for them was can be done more elegantly with CSS.*The iframe element will not replace the body of a page. Within the same page body using iframe will include a new browsing context embedded within a block of content. Bookmarking still functions as it should. It works better than the frameset model and is used when the developer needs to include an embedded browsing context such as a Google calendar within a web page.