W3C home > Mailing lists > Public > public-html-diffs@w3.org > May 2009

Elaborate on willful violations. (whatwg r3138)

From: poot <cvsmail@w3.org>
Date: Tue, 26 May 2009 19:31:48 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090526103148.D8F592BC66@toro.w3.mag.keio.ac.jp>
Elaborate on willful violations. (whatwg r3138)

Diffs for this change per section: 
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#script-s-global-object
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#misinterpreted-for-compatibility
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#algorithm-for-extracting-an-encoding-from-a-content-type
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#constructing-form-data-set
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#url-host-specific
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#content-type-sniffing:-web-pages
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2296.html#writing-cache-manifests

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2295&r2=1.2296&f=h
http://html5.org/tools/web-apps-tracker?from=3137&to=3138

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2295
retrieving revision 1.2296
diff -u -d -r1.2295 -r1.2296
--- Overview.html	26 May 2009 10:15:38 -0000	1.2295
+++ Overview.html	26 May 2009 10:30:14 -0000	1.2296
@@ -4149,8 +4149,8 @@
   </ol><!-- XXX we might want to define "server-based naming authority",
   it's not clear RFC3986 does a good job of defining that anymore
   (earlier URI specs did) --><p class="note">These parsing rules are a <a href="#willful-violation">willful
-  violation</a> of RFC 3986 and RFC 3987 to handle legacy
-  content. <a href="#references">[RFC3986]</a> <a href="#references">[RFC3987]</a></p>
+  violation</a> of RFC 3986 and RFC 3987 (which do not define error
+  handling), motivated by a desire to handle legacy content. <a href="#references">[RFC3986]</a> <a href="#references">[RFC3987]</a></p>
 
   </div><div class="impl">
 
@@ -4824,8 +4824,10 @@
 
     </dl></li>
 
-  </ol><p class="note">The above algorithm is a <a href="#willful-violation">willful violation</a> of the
-  HTTP specification. <a href="#references">[HTTP]</a></p>
+  </ol><p class="note">The above algorithm is a <a href="#willful-violation">willful
+  violation</a> of the HTTP specification, which requires that the
+  Content-Type headers be honored, despite implementation experience
+  showing that this is not pratical in many cases. <a href="#references">[HTTP]</a></p>
 
 
   <h4 id="content-type-sniffing:-web-pages"><span class="secno">2.7.2 </span>Content-Type sniffing: Web pages</h4>
@@ -5419,8 +5421,9 @@
     <tr><td> x-x-big5 <td> Big5 <td>
          <a href="#references">[BIG5]</a> <!-- XXX ? -->
    </table><p class="note">The requirement to treat certain encodings as other
-  encodings according to the table above is a <a href="#willful-violation">willful violation</a> of the
-  W3C Character Model specification. <a href="#references">[CHARMOD]</a></p>
+  encodings according to the table above is a <a href="#willful-violation">willful
+  violation</a> of the W3C Character Model specification, motivated
+  by a desire for compatibility with legacy content. <a href="#references">[CHARMOD]</a></p>
 
   <hr><p>User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU
   encodings. <a href="#references">[CESU8]</a> <a href="#references">[UTF7]</a> <a href="#references">[BOCU1]</a> <a href="#references">[SCSU]</a></p>
@@ -31954,7 +31957,10 @@
 
     <p>If <var title="">action</var> is the empty string, let <var title="">action</var> be <a href="#the-document-s-address">the document's address</a>.</p>
 
-    <p class="note">This step is a <a href="#willful-violation">willful violation</a> of RFC 3986. <a href="#references">[RFC3986]</a></p>
+    <p class="note">This step is a <a href="#willful-violation">willful violation</a> of
+    RFC 3986, which would require base URL processing here. This
+    violation is motivated by a desire for compatibility with legacy
+    content. <a href="#references">[RFC3986]</a></p>
 
     <!-- Don't ask me why. But that's what IE does. It even treats
     action="" differently from action=" " or action="#" (the latter
@@ -42341,9 +42347,12 @@
     <code><a href="#window">Window</a></code> object, then in JavaScript, the <code title="">this</code> keyword in the global scope must return the
     <code><a href="#window">Window</a></code> object's <code><a href="#windowproxy">WindowProxy</a></code> object.</p>
 
-    <p class="note">This is a <a href="#willful-violation">willful violation</a> of the JavaScript
-    specification current at the time of writing (ECMAScript edition
-    3). <a href="#references">[ECMA262]</a></p>
+    <p class="note">This is a <a href="#willful-violation">willful violation</a> of the
+    JavaScript specification current at the time of writing
+    (ECMAScript edition 3). The JavaScript specification requires that
+    the code title=""&gt;this keyword in the global scope return
+    the global object, but this is not compatible with the security
+    design prevalent in implementations as specified herein. <a href="#references">[ECMA262]</a></p>
 
    </dd>
 
@@ -44492,12 +44501,13 @@
   line-based. Newlines must be represented by U+000A LINE FEED (LF)
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
   CARRIAGE RETURN (CR) U+000A LINE FEED (LF) pairs.<p class="note">This is a <a href="#willful-violation" title="willful violation">willful
-  double violation</a> of RFC2046. <a href="#references">[RFC2046]</a></p><!-- 2046 (and 2045) says that
-  charset="" is always allowed on text/*, but that harks back to the
-  old days before UTF-8 was widely used; 2046 also says that newlines
-  are always CRLF-delimited, which is not workable given the
-  widespread use of editors that use either lone LFs or lone CRs as
-  line break delimiters. --><p>The first line of an application cache manifest must consist of
+  double violation</a> of RFC2046, which requires all <code title="">text/*</code> types to support an open-ended set of
+  character encodings and only allows CRLF line breaks. These
+  requirements, however, are outdated; UTF-8 is now widely used, such
+  that supporting other encodings is no longer necessary, and use of
+  CR, LF, and CRLF line breaks is commonly supported and indeed
+  sometimes CRLF is <em>not</em> supported by text editors. <a href="#references">[RFC2046]</a></p><!-- also RFC 2045 for charset
+  --><p>The first line of an application cache manifest must consist of
   the string "CACHE", a single U+0020 SPACE character, the string
   "MANIFEST", and either a U+0020 SPACE character, a U+0009 CHARACTER
   TABULATION (tab) character, a U+000A LINE FEED (LF) character, or a
Received on Tuesday, 26 May 2009 10:32:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:05 GMT