![]()
Creates a completely blank iframe element.
The iframe will not caused mixed-content warnings for IE6 under HTTPS.
The iframe will also have no borders or padding, so that the styled width
and height will be the actual width and height of the iframe.
This function currently only attempts to create a blank iframe. There
are no guarantees to the contents of the iframe or whether it is rendered
in quirks mode.
Arguments:
Returns: !HTMLIFrameElement
A completely blank iframe.
|
code » | ||||||
![]()
Creates a same-domain iframe containing preloaded content.
This is primarily useful for DOM sandboxing. One use case is to embed
a trusted Javascript app with potentially conflicting CSS styles. The
second case is to reduce the cost of layout passes by the browser -- for
example, you can perform sandbox sizing of characters in an iframe while
manipulating a heavy DOM in the main window. The iframe and parent frame
can access each others' properties and functions without restriction.
Arguments:
Returns: !HTMLIFrameElement
An iframe that has the specified contents.
|
code » | ||||||
![]()
Writes the contents of a blank iframe that has already been inserted
into the document.
Arguments:
|
code » |
![]()
Safe source for a blank iframe.
Intentionally not about:blank, which gives mixed content warnings in IE6
over HTTPS.
|
Code » | |
![]()
Safe source for a new blank iframe that may not cause a new load of the
iframe. This is different from
goog.dom.iframe.BLANK_SOURCE in that
it will allow an iframe to be loaded synchronously in more browsers, notably
Gecko, following the javascript protocol spec.
NOTE: This should not be used to replace the source of an existing iframe.
The new src value will be ignored, per the spec.
Due to cross-browser differences, the load is not guaranteed to be
synchronous. If code depends on the load of the iframe,
then goog.net.IframeLoadMonitor or a similar technique should be
used.
According to
http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#javascript-protocol
the 'javascript:""' URL should trigger a new load of the iframe, which may be
asynchronous. A void src, such as 'javascript:undefined', does not change
the browsing context document's, and thus should not trigger another load.
Intentionally not about:blank, which also triggers a load.
NOTE: 'javascript:' URL handling spec compliance varies per browser. IE
throws an error with 'javascript:undefined'. Webkit browsers will reload the
iframe when setting this source on an existing iframe.
|
Code » | |
![]()
Styles to help ensure an undecorated iframe.
|
Code » |