- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 18 Feb 2010 03:30:12 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv5699 Modified Files: Overview.html Log Message: readability (whatwg r4776) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3823 retrieving revision 1.3824 diff -u -d -r1.3823 -r1.3824 --- Overview.html 18 Feb 2010 03:28:00 -0000 1.3823 +++ Overview.html 18 Feb 2010 03:30:08 -0000 1.3824 @@ -7458,10 +7458,10 @@ documents, these contexts could be inside elements from other namespaces, if those elements are defined as providing the relevant contexts.<div class="example"> - <p>The Atom specification defines the Atom <code title="">content</code> element, when its <code title="">type</code> attribute has the value <code title="">xhtml</code>, as requiring that it contains a single HTML - <code><a href="#the-div-element">div</a></code> element. Thus, a <code><a href="#the-div-element">div</a></code> element is - allowed in that context, even though this is not explicitly - normatively stated by this specification. <a href="#refsATOM">[ATOM]</a></p> + <p>For example, the Atom specification defines a <code title="">content</code> element. When its <code title="">type</code> attribute has the value <code title="">xhtml</code>, the Atom specification requires that it + contain a single HTML <code><a href="#the-div-element">div</a></code> element. Thus, a + <code><a href="#the-div-element">div</a></code> element is allowed in that context, even though + this is not explicitly normatively stated by this specification. <a href="#refsATOM">[ATOM]</a></p> </div><p>In addition, <a href="#html-elements">HTML elements</a> may be orphan nodes (i.e. without a parent node).<div class="example">
Received on Thursday, 18 February 2010 03:30:13 UTC