[html5] r3280 - [ac] (0) <iframe> content model.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-16 12:14:23 -0700 (Tue, 16 Jun 2009)
New Revision: 3280

Modified:
   index
   source
Log:
[ac] (0) <iframe> content model.

Modified: index
===================================================================
--- index	2009-06-16 18:55:34 UTC (rev 3279)
+++ index	2009-06-16 19:14:23 UTC (rev 3280)
@@ -18221,15 +18221,21 @@
   <code><a href=#the-iframe-element>iframe</a></code> elements, the contents would be parsed as markup
   that could act as fallback content.)</p>
 
-  <p>The content model of <code><a href=#the-iframe-element>iframe</a></code> elements is text, except
-  that the text must be such that <span class=XXX>... anyone
-  have any bright ideas?</span></p>
-  <!--XXX
-    Gotta handle <script> elements inside <iframe>s that screw around with the DOM on the fly, or that use document.write().
-    Gotta handle <iframe> elements created from script with text contents.
-    Gotta handle the XML case.
-   -->
+  <p>When used in <a href=#html-documents>HTML documents</a>, the allowed content
+  model of <code><a href=#the-iframe-element>iframe</a></code> elements is text, except that invoking
+  the <a href=#html-fragment-parsing-algorithm>HTML fragment parsing algorithm</a> with the
+  <code><a href=#the-iframe-element>iframe</a></code> element as the <var title="">context</var>
+  element and the text contents as the <var title="">input</var> must
+  result in a list of nodes that are all <a href=#phrasing-content-0>phrasing
+  content</a>, with no <a href=#parse-error title="parse error">parse
+  errors</a> having occurred, with no <code><a href=#script>script</a></code> elements
+  being anywhere in the list or as descendants of elements in the
+  list, and with all the elements in the list (including their
+  descendants) being themselves conforming.</p>
 
+  <p>The <code><a href=#the-iframe-element>iframe</a></code> element must be empty in <a href=#xml-documents>XML
+  documents</a>.</p>
+
   <p class=note>The <a href=#html-parser>HTML parser</a> treats markup inside
   <code><a href=#the-iframe-element>iframe</a></code> elements as text.</p>
 

Modified: source
===================================================================
--- source	2009-06-16 18:55:34 UTC (rev 3279)
+++ source	2009-06-16 19:14:23 UTC (rev 3280)
@@ -19402,15 +19402,21 @@
   <code>iframe</code> elements, the contents would be parsed as markup
   that could act as fallback content.)</p>
 
-  <p>The content model of <code>iframe</code> elements is text, except
-  that the text must be such that <span class="XXX">... anyone
-  have any bright ideas?</span></p>
-  <!--XXX
-    Gotta handle <script> elements inside <iframe>s that screw around with the DOM on the fly, or that use document.write().
-    Gotta handle <iframe> elements created from script with text contents.
-    Gotta handle the XML case.
-   -->
+  <p>When used in <span>HTML documents</span>, the allowed content
+  model of <code>iframe</code> elements is text, except that invoking
+  the <span>HTML fragment parsing algorithm</span> with the
+  <code>iframe</code> element as the <var title="">context</var>
+  element and the text contents as the <var title="">input</var> must
+  result in a list of nodes that are all <span>phrasing
+  content</span>, with no <span title="parse error">parse
+  errors</span> having occurred, with no <code>script</code> elements
+  being anywhere in the list or as descendants of elements in the
+  list, and with all the elements in the list (including their
+  descendants) being themselves conforming.</p>
 
+  <p>The <code>iframe</code> element must be empty in <span>XML
+  documents</span>.</p>
+
   <p class="note">The <span>HTML parser</span> treats markup inside
   <code>iframe</code> elements as text.</p>