[html5] r5565 - [e] (0) List some of the differences, to make Julian happier. Fixing http://www. [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-09-29 20:58:32 -0700 (Wed, 29 Sep 2010)
New Revision: 5565

Modified:
   complete.html
   index
   source
Log:
[e] (0) List some of the differences, to make Julian happier.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10804

Modified: complete.html
===================================================================
--- complete.html	2010-09-30 01:46:42 UTC (rev 5564)
+++ complete.html	2010-09-30 03:58:32 UTC (rev 5565)
@@ -6572,8 +6572,12 @@
     </dl></li>
 
   </ol><p class=note>This requirement is a <a href=#willful-violation>willful violation</a>
-  of the HTTP specification, motivated by the need for backwards
-  compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>
+  of the HTTP specification (for example, HTTP doesn't allow the use
+  of single quotes and requires supporting a backslash-escape
+  mechanism that is not supported by this algorithm<!-- not to mention
+  not having any rules for error-handling, which is of course why
+  we're having to define it ourselves -->), motivated by the need for
+  backwards compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>
 
   </div>
 

Modified: index
===================================================================
--- index	2010-09-30 01:46:42 UTC (rev 5564)
+++ index	2010-09-30 03:58:32 UTC (rev 5565)
@@ -6549,8 +6549,12 @@
     </dl></li>
 
   </ol><p class=note>This requirement is a <a href=#willful-violation>willful violation</a>
-  of the HTTP specification, motivated by the need for backwards
-  compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>
+  of the HTTP specification (for example, HTTP doesn't allow the use
+  of single quotes and requires supporting a backslash-escape
+  mechanism that is not supported by this algorithm<!-- not to mention
+  not having any rules for error-handling, which is of course why
+  we're having to define it ourselves -->), motivated by the need for
+  backwards compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>
 
   </div>
 

Modified: source
===================================================================
--- source	2010-09-30 01:46:42 UTC (rev 5564)
+++ source	2010-09-30 03:58:32 UTC (rev 5565)
@@ -6231,8 +6231,12 @@
   </ol>
 
   <p class="note">This requirement is a <span>willful violation</span>
-  of the HTTP specification, motivated by the need for backwards
-  compatibility with legacy content. <a
+  of the HTTP specification (for example, HTTP doesn't allow the use
+  of single quotes and requires supporting a backslash-escape
+  mechanism that is not supported by this algorithm<!-- not to mention
+  not having any rules for error-handling, which is of course why
+  we're having to define it ourselves -->), motivated by the need for
+  backwards compatibility with legacy content. <a
   href="#refsHTTP">[HTTP]</a></p>
 
   </div>