[html5] r1659 - /
whatwg at whatwg.org
whatwg at whatwg.org
Wed May 21 15:30:32 PDT 2008
Author: ianh
Date: 2008-05-21 15:30:31 -0700 (Wed, 21 May 2008)
New Revision: 1659
Modified:
index
source
Log:
[c] (0) Add height/width to <iframe>.
Modified: index
===================================================================
--- index 2008-05-21 22:22:58 UTC (rev 1658)
+++ index 2008-05-21 22:30:31 UTC (rev 1659)
@@ -14185,6 +14185,10 @@
<dd><code title=attr-iframe-seamless><a
href="#seamless">seamless</a></code>
+ <dd><code title=attr-dim-width><a href="#width4">width</a></code>
+
+ <dd><code title=attr-dim-height><a href="#height3">height</a></code>
+
<dt>DOM interface:
<dd>
@@ -14193,10 +14197,13 @@
attribute DOMString <a href="#src2" title=dom-iframe-src>src</a>;
attribute DOMString <a href="#name2" title=dom-iframe-name>name</a>;
attribute DOMString <a href="#sandbox0" title=dom-iframe-sandbox>sandbox</a>;
- attribute boolean <a href="#seamless1" title=dom-iframe-seamless>seamless</a>;<!--
+ attribute boolean <a href="#seamless1" title=dom-iframe-seamless>seamless</a>;
+ attribute long <a href="#width5" title=dom-dim-width>width</a>;
+ attribute long <a href="#height4" title=dom-dim-height>height</a>;
+<!-- XXX we should bring these back since the Window spec has atrophied
readonly attribute Document <span title="dom-iframe-contentDocument">contentDocument</span>;
- readonly attribute <span>Window</span> <span title="dom-iframe-contentWindow">contentWindow</span>;-->
-};</pre>
+ readonly attribute <span>Window</span> <span title="dom-iframe-contentWindow">contentWindow</span>;
+-->};</pre>
<p>Objects implementing the <code><a
href="#htmliframeelement">HTMLIFrameElement</a></code> interface must
@@ -14533,6 +14540,11 @@
<hr>
+ <p>The <code><a href="#iframe">iframe</a></code> element supports <a
+ href="#dimension0">dimension attributes</a> for cases where the embedded
+ content has specific dimensions (e.g. ad units have well-defined
+ dimensions).
+
<p>An <code><a href="#iframe">iframe</a></code> element never has <a
href="#fallback">fallback content</a>, as it will always create a nested
<a href="#browsing1">browsing context</a>, regardless of whether the
Modified: source
===================================================================
--- source 2008-05-21 22:22:58 UTC (rev 1658)
+++ source 2008-05-21 22:30:31 UTC (rev 1659)
@@ -12209,16 +12209,21 @@
<dd><code title="attr-iframe-name">name</code></dd>
<dd><code title="attr-iframe-sandbox">sandbox</code></dd>
<dd><code title="attr-iframe-seamless">seamless</code></dd>
+ <dd><code title="attr-dim-width">width</code></dd>
+ <dd><code title="attr-dim-height">height</code></dd>
<dt>DOM interface:</dt>
<dd>
<pre class="idl">interface <dfn>HTMLIFrameElement</dfn> : <span>HTMLElement</span> {
attribute DOMString <span title="dom-iframe-src">src</span>;
attribute DOMString <span title="dom-iframe-name">name</span>;
attribute DOMString <span title="dom-iframe-sandbox">sandbox</span>;
- attribute boolean <span title="dom-iframe-seamless">seamless</span>;<!--
+ attribute boolean <span title="dom-iframe-seamless">seamless</span>;
+ attribute long <span title="dom-dim-width">width</span>;
+ attribute long <span title="dom-dim-height">height</span>;
+<!-- XXX we should bring these back since the Window spec has atrophied
readonly attribute Document <span title="dom-iframe-contentDocument">contentDocument</span>;
- readonly attribute <span>Window</span> <span title="dom-iframe-contentWindow">contentWindow</span>;-->
-};</pre>
+ readonly attribute <span>Window</span> <span title="dom-iframe-contentWindow">contentWindow</span>;
+-->};</pre>
<p>Objects implementing the <code>HTMLIFrameElement</code>
interface must also implement the <code>EmbeddingElement</code>
interface defined in the Window Object specification. <a
@@ -12586,6 +12591,10 @@
+ <p>The <code>iframe</code> element supports <span>dimension
+ attributes</span> for cases where the embedded content has specific
+ dimensions (e.g. ad units have well-defined dimensions).</p>
+
<p>An <code>iframe</code> element never has <span>fallback
content</span>, as it will always create a nested <span>browsing
context</span>, regardless of whether the specified initial contents
More information about the Commit-Watchers
mailing list