The following lines were added (+) and removed (-):
=== Busting Frame Busting JavaScript ====== Defeat Frame Busting JavaScript ===aka: Busting Frame Busting JavaScript<BR><small>''Frame Buster Buster using 204 status verified working on Google Chrome Version 71.0.3578.98 (Official Build) (64-bit) April 2019.''</small>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 forThe <iframe> creates an inline frame, which embeds an independent HTML document into the current document.Example: <nowiki><iframe width="560" height="315" src="https://www.youtube.com/embed/nicolep" frameborder="0" allowfullscreen></iframe></nowiki>In HTML 4.01, the height could be defined in pixels or in % of the containing element. In HTML5, the value must be in pixels.iframe using CSS for HTML5 iframe { width: 100%; height: 100%; }Note that the height attribute will not work like this. With will, not not height. You have to specify height for the parents of iframe, in this case body and html. html,body{ height: 100%; } iframe{ width:60%; height:70% }This way you have a PERCENTAGE as with and height that is functional under the HTML5 standard== HTML5 Does Away with Frames, Mostly ==* frames by frameset are dead* iframe frames live on, with some changesThe <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.Not all of the HTML5 changes are positive. Although it is positive to do away with frameset, HTML5 changes to iframe are bad in that they force CSS onto the developer. The Nerds behind this stuff want to shove as much CSS on developers as possible. The original intent of the web was to allow flexibility in creating a pure HTML web site. HTML5 nerds want to force CSS on us. We learn that iframe no longer allows you to specify width and height as attributes in the tag. Instead, this is all handled with CSS.