- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 10 Aug 2010 06:19:38 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv30831
Modified Files:
Overview.html
Log Message:
More clarifications. (whatwg r5266)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4194
retrieving revision 1.4195
diff -u -d -r1.4194 -r1.4195
--- Overview.html 10 Aug 2010 06:14:17 -0000 1.4194
+++ Overview.html 10 Aug 2010 06:19:34 -0000 1.4195
@@ -33722,11 +33722,12 @@
form "c", while the <a href="#form-owner">form owner</a> of "e" would be the
outer form "a".</p>
- <p>This is because despite the association of "e" with "c" in the
- <a href="#html-parser">HTML parser</a>, when the <code title="dom-innerHTML"><a href="#dom-innerhtml">innerHTML</a></code> algorithm moves the nodes
- from the temporary document to the "b" element, the nodes see their
- ancestor chain change, and thus all the "magic" associations done
- by the parser are reset to normal ancestor associations.</p>
+ <p>This happens as follows: First, the "e" node gets associated
+ with "c" in the <a href="#html-parser">HTML parser</a>. Theh, the <code title="dom-innerHTML"><a href="#dom-innerhtml">innerHTML</a></code> algorithm moves the nodes
+ from the temporary document to the "b" element. At this point, the
+ nodes see their ancestor chain change, and thus all the "magic"
+ associations done by the parser are reset to normal ancestor
+ associations.</p>
<p>This example is a non-conforming document, though, as it is a
violation of the content models to nest <code><a href="#the-form-element">form</a></code>
@@ -35138,9 +35139,9 @@
<p>If the <code><a href="#the-form-element">form</a></code> element has an <code title="attr-form-accept-charset"><a href="#attr-form-accept-charset">accept-charset</a></code> attribute,
then, taking into account the characters found in the <var title="">form data set</var>'s names and values, and the character
encodings supported by the user agent, select a character encoding
- from the list given in the <code><a href="#the-form-element">form</a></code>'s <code title="attr-form-accept-charset"><a href="#attr-form-accept-charset">accept-charset</a></code>
- attribute. If none of the encodings are supported, then let the
- selected character encoding be UTF-8.</p>
+ from the list given in the <code><a href="#the-form-element">form</a></code>'s <code title="attr-form-accept-charset"><a href="#attr-form-accept-charset">accept-charset</a></code> attribute.
+ If none of the encodings are supported, or if none are listed,
+ then let the selected character encoding be UTF-8.</p>
<p>Otherwise, the selected character encoding is the
<a href="#document-s-character-encoding">document's character encoding</a>.</p>
Received on Tuesday, 10 August 2010 06:19:40 UTC