Changes

Frames, JavaScript and HTML

1,427 bytes added, 16:16, 19 April 2019
/* Busting Frame Busting JavaScript */
The following lines were added (+) and removed (-):
=== Busting Frame Busting JavaScript ====== Defeat Frame Busting JavaScript ===aka: Busting Frame Busting JavaScript<BR>The <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* frames by frameset are dead* iframe frames live on, with some changes 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. 
Bureaucrat, administrator
16,192
edits