Browse files

[giow] (3) When a page interpreted as UTF-8 has a <meta charset> sayi…

…ng UTF-16, the spec used to say to reload even though the encoding didn't change.

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

git-svn-id: http://svn.whatwg.org/webapps@6814 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent 4e0d8e0 commit 132b83d5bafaf55e007a6322b39a5dc1951b0320 @Hixie Hixie committed Nov 2, 2011
Showing with 30 additions and 30 deletions.
  1. +10 −10 complete.html
  2. +10 −10 index
  3. +10 −10 source
View
20 complete.html
@@ -84404,7 +84404,16 @@ <h5 id=changing-the-encoding-while-parsing><span class=secno>13.2.2.4 </span>Cha
failed to find an encoding, or if it found an encoding that was not
the actual encoding of the file.</p>
- <ol><li>If the new encoding is identical or equivalent to the encoding
+ <ol><li>If the encoding that is already being used to interpret the
+ input stream is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, then set the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> to
+ <i>certain</i> and abort these steps. The new encoding is ignored;
+ if it was anything but the same encoding, then it would be clearly
+ incorrect.</li>
+
+ <li>If the new encoding is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, change
+ it to UTF-8.</li>
+
+ <li>If the new encoding is identical or equivalent to the encoding
that is already being used to interpret the input stream, then set
the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> to
<i>certain</i> and abort these steps. This happens when the
@@ -84414,15 +84423,6 @@ <h5 id=changing-the-encoding-while-parsing><span class=secno>13.2.2.4 </span>Cha
pass found that the encoding sniffing algorithm described in the
earlier section failed to find the right encoding.</li>
- <li>If the encoding that is already being used to interpret the
- input stream is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, then set the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> to
- <i>certain</i> and abort these steps. The new encoding is ignored;
- if it was anything but the same encoding, then it would be clearly
- incorrect.</li>
-
- <li>If the new encoding is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, change
- it to UTF-8.</li>
-
<li>If all the bytes up to the last byte converted by the current
decoder have the same Unicode interpretations in both the current
encoding and the new encoding, and if the user agent supports
View
20 index
@@ -84404,7 +84404,16 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
failed to find an encoding, or if it found an encoding that was not
the actual encoding of the file.</p>
- <ol><li>If the new encoding is identical or equivalent to the encoding
+ <ol><li>If the encoding that is already being used to interpret the
+ input stream is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, then set the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> to
+ <i>certain</i> and abort these steps. The new encoding is ignored;
+ if it was anything but the same encoding, then it would be clearly
+ incorrect.</li>
+
+ <li>If the new encoding is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, change
+ it to UTF-8.</li>
+
+ <li>If the new encoding is identical or equivalent to the encoding
that is already being used to interpret the input stream, then set
the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> to
<i>certain</i> and abort these steps. This happens when the
@@ -84414,15 +84423,6 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
pass found that the encoding sniffing algorithm described in the
earlier section failed to find the right encoding.</li>
- <li>If the encoding that is already being used to interpret the
- input stream is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, then set the <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> to
- <i>certain</i> and abort these steps. The new encoding is ignored;
- if it was anything but the same encoding, then it would be clearly
- incorrect.</li>
-
- <li>If the new encoding is <a href=#a-utf-16-encoding>a UTF-16 encoding</a>, change
- it to UTF-8.</li>
-
<li>If all the bytes up to the last byte converted by the current
decoder have the same Unicode interpretations in both the current
encoding and the new encoding, and if the user agent supports
View
20 source
@@ -95619,16 +95619,6 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
<ol>
- <li>If the new encoding is identical or equivalent to the encoding
- that is already being used to interpret the input stream, then set
- the <span title="concept-encoding-confidence">confidence</span> to
- <i>certain</i> and abort these steps. This happens when the
- encoding information found in the file matches what the
- <span>encoding sniffing algorithm</span> determined to be the
- encoding, and in the second pass through the parser if the first
- pass found that the encoding sniffing algorithm described in the
- earlier section failed to find the right encoding.</li>
-
<li>If the encoding that is already being used to interpret the
input stream is <span>a UTF-16 encoding</span>, then set the <span
title="concept-encoding-confidence">confidence</span> to
@@ -95639,6 +95629,16 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
<li>If the new encoding is <span>a UTF-16 encoding</span>, change
it to UTF-8.</li>
+ <li>If the new encoding is identical or equivalent to the encoding
+ that is already being used to interpret the input stream, then set
+ the <span title="concept-encoding-confidence">confidence</span> to
+ <i>certain</i> and abort these steps. This happens when the
+ encoding information found in the file matches what the
+ <span>encoding sniffing algorithm</span> determined to be the
+ encoding, and in the second pass through the parser if the first
+ pass found that the encoding sniffing algorithm described in the
+ earlier section failed to find the right encoding.</li>
+
<li>If all the bytes up to the last byte converted by the current
decoder have the same Unicode interpretations in both the current
encoding and the new encoding, and if the user agent supports

0 comments on commit 132b83d

Please sign in to comment.