W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2009

html5/spec Overview.html,1.2426,1.2427

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 16 Jun 2009 19:14:31 +0000
To: public-html-commits@w3.org
Message-Id: <E1MGe75-0007nG-R4@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv29944

Modified Files:
	Overview.html 
Log Message:
<iframe> content model. (whatwg r3280)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2426
retrieving revision 1.2427
diff -u -d -r1.2426 -r1.2427
--- Overview.html	16 Jun 2009 18:55:39 -0000	1.2426
+++ Overview.html	16 Jun 2009 19:14:28 -0000	1.2427
@@ -15758,13 +15758,18 @@
   are successfully used.<p>Descendants of <code><a href="#the-iframe-element">iframe</a></code> elements represent
   nothing. (In legacy user agents that do not support
   <code><a href="#the-iframe-element">iframe</a></code> elements, the contents would be parsed as markup
-  that could act as fallback content.)<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 class="note">The <a href="#html-parser">HTML parser</a> treats markup inside
+  that could act as fallback content.)<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>The <code><a href="#the-iframe-element">iframe</a></code> element must be empty in <a href="#xml-documents">XML
+  documents</a>.<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.<div class="impl">
 
   <p>The DOM attributes <dfn id="dom-iframe-src" title="dom-iframe-src"><code>src</code></dfn>, <dfn id="dom-iframe-name" title="dom-iframe-name"><code>name</code></dfn>, <dfn id="dom-iframe-sandbox" title="dom-iframe-sandbox"><code>sandbox</code></dfn>, and <dfn id="dom-iframe-seamless" title="dom-iframe-seamless"><code>seamless</code></dfn> must
Received on Tuesday, 16 June 2009 19:28:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 16 June 2009 19:28:40 GMT