[e] (0) Mention that sniffing the encoding violates HTTP.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7949

git-svn-id: http://svn.whatwg.org/webapps@4248 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -69927,6 +69927,15 @@ <h5 id=determining-the-character-encoding><span class=secno>11.2.2.1 </span>Dete
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class=note>This algorithm is a <a href=#willful-violation>willful violation</a>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <a href=#character-encoding-declaration>character
+  encoding declaration</a> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <a href=#character-encoding-declaration>character encoding declaration</a> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a href=#refsHTTP>[HTTP]</a> <a href=#refsRFC2046>[RFC2046]</a></p>
+
 
   <h5 id=character-encodings-0><span class=secno>11.2.2.2 </span>Character encodings</h5>
 

index

@@ -60990,6 +60990,15 @@ interface <dfn id=messageport>MessagePort</dfn> {
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class=note>This algorithm is a <a href=#willful-violation>willful violation</a>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <a href=#character-encoding-declaration>character
+  encoding declaration</a> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <a href=#character-encoding-declaration>character encoding declaration</a> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a href=#refsHTTP>[HTTP]</a> <a href=#refsRFC2046>[RFC2046]</a></p>
+
 
   <h5 id=character-encodings-0><span class=secno>9.2.2.2 </span>Character encodings</h5>
 

source

@@ -78683,6 +78683,16 @@ interface <dfn>MessagePort</dfn> {
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class="note">This algorithm is a <span>willful violation</span>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <span>character
+  encoding declaration</span> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <span>character encoding declaration</span> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a
+  href="#refsHTTP">[HTTP]</a> <a href="#refsRFC2046">[RFC2046]</a></p>
+
 
   <h5>Character encodings</h5>