[html5] r1674 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2008-05-22 16:30:54 -0700 (Thu, 22 May 2008)
New Revision: 1674

Modified:
   index
   source
Log:
[acgio] (2) Bring things more in line with the requirements of actual web content

Modified: index
===================================================================
--- index	2008-05-22 22:41:43 UTC (rev 1673)
+++ index	2008-05-22 23:30:54 UTC (rev 1674)
@@ -30481,7 +30481,8 @@
    RETURN (CR) characters, or U+000D CARRIAGE RETURN (CR) U+000A LINE FEED
    (LF) pairs.
 
-  <p class=note>This is a willful double violation of RFC2046.
+  <p class=note>This is a willful double violation of RFC2046. <a
+   href="#refsRFC2046">[RFC2046]</a>
 
   <p>The first line of an application cache manifest must consist of the
    string "CACHE", a single U+0020 SPACE character, the string "MANIFEST",
@@ -33743,23 +33744,12 @@
 
   <ol>
    <li>
-    <p>Skip characters in <var title="">s</var> up to and including the first
-     U+003B SEMICOLON (<code title="">;</code>) character.
+    <p>Find the first seven characters in <var title="">s</var> that are a
+     case-insensitive<!-- XXX ASCII--> match for the word 'charset'. If no
+     such match is found, return nothing.</p>
 
    <li>
     <p>Skip any U+0009, U+000A, U+000B, U+000C, U+000D, or U+0020 characters
-     (i.e. spaces) that immediately follow the semicolon.
-
-   <li>
-    <p>If the next seven characters are not a case-insensitive<!--
-   XXX ASCII-->
-     match for 'charset', return nothing.
-   </li>
-   <!-- XXX technically, we should skip to the next MIME parameter,
-   but the question is, do browsers do that? -->
-
-   <li>
-    <p>Skip any U+0009, U+000A, U+000B, U+000C, U+000D, or U+0020 characters
      that immediately follow the word 'charset' (there might not be any).
 
    <li>
@@ -33788,6 +33778,8 @@
 
      <dt>If it is an unmatched U+0027 APOSTROPHE ("'")
 
+     <dt>If there is no next character
+
      <dd>
       <p>Return nothing.
 
@@ -33800,6 +33792,9 @@
     </dl>
   </ol>
 
+  <p class=note>The above algorithm is a willful violation of the HTTP
+   specification. <a href="#refsRFC2616">[RFC2616]</a>
+
   <h3 id=structured><span class=secno>4.11 </span>Structured client-side
    storage</h3>
 

Modified: source
===================================================================
--- source	2008-05-22 22:41:43 UTC (rev 1673)
+++ source	2008-05-22 23:30:54 UTC (rev 1674)
@@ -28321,7 +28321,8 @@
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.</p>
 
-  <p class="note">This is a willful double violation of RFC2046.</p>
+  <p class="note">This is a willful double violation of RFC2046. <a
+  href="#refsRFC2046">[RFC2046]</a></p>
 
   <p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string
@@ -31553,20 +31554,11 @@
 
   <ol>
 
-   <li><p>Skip characters in <var title="">s</var> up to and including
-   the first U+003B SEMICOLON (<code title="">;</code>)
-   character.</p></li>
+   <li><p>Find the first seven characters in <var title="">s</var>
+   that are a case-insensitive<!-- XXX ASCII--> match for the word
+   'charset'. If no such match is found, return nothing.</p>
 
    <li><p>Skip any U+0009, U+000A, U+000B, U+000C, U+000D, or U+0020
-   characters (i.e. spaces) that immediately follow the
-   semicolon.</p></li>
-
-   <li><p>If the next seven characters are not a case-insensitive<!--
-   XXX ASCII--> match for 'charset', return nothing.</p></li>
-   <!-- XXX technically, we should skip to the next MIME parameter,
-   but the question is, do browsers do that? -->
-
-   <li><p>Skip any U+0009, U+000A, U+000B, U+000C, U+000D, or U+0020
    characters that immediately follow the word 'charset' (there might
    not be any).</p></li>
 
@@ -31590,11 +31582,14 @@
      <dd><p>Return the string between this character and the next
      earliest occurrence of this character.</dd>
 
+
      <dt>If it is an unmatched U+0022 QUOTATION MARK ('"')</dt>
      <dt>If it is an unmatched U+0027 APOSTROPHE ("'")</dt>
+     <dt>If there is no next character</dt>
 
      <dd><p>Return nothing.</dd>
 
+
      <dt>Otherwise</dt>
 
      <dd><p>Return the string from this character to the first U+0009,
@@ -31607,6 +31602,8 @@
 
   </ol>
 
+  <p class="note">The above algorithm is a willful violation of the
+  HTTP specification. <a href="#refsRFC2616">[RFC2616]</a></p>