- From: poot <cvsmail@w3.org>
- Date: Sun, 26 Sep 2010 04:36:34 +0900 (JST)
- To: public-html-diffs@w3.org
hixie: xref for easier finding of the prose now that this section is so long (whatwg r5498) http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4388&r2=1.4389&f=h http://html5.org/tools/web-apps-tracker?from=5497&to=5498 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.4388 retrieving revision 1.4389 diff -u -d -r1.4388 -r1.4389 --- Overview.html 25 Sep 2010 19:32:52 -0000 1.4388 +++ Overview.html 25 Sep 2010 19:36:20 -0000 1.4389 @@ -18699,7 +18699,7 @@ <dt>Contexts in which this element can be used:</dt> <dd>Where <a href="#embedded-content">embedded content</a> is expected.</dd> <dt>Content model:</dt> - <dd>Text that conforms to the requirements given in the prose.</dd> + <dd>Text that conforms to <a href="#iframe-content-model">the requirements given in the prose</a>.</dd> <dt>Content attributes:</dt> <dd><a href="#global-attributes">Global attributes</a></dd> <dd><code title="attr-iframe-src"><a href="#attr-iframe-src">src</a></code></dd> @@ -19401,17 +19401,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>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">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 + that could act as fallback content.)<p id="iframe-content-model">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">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">
Received on Saturday, 25 September 2010 19:37:02 UTC