[html5] r2953 - [e] (0) Visit the confessional. (credit: sb) (bug 6684)

[whatwg at whatwg.org]

Author: ianh
Date: 2009-04-01 11:21:44 -0700 (Wed, 01 Apr 2009)
New Revision: 2953

Modified:
   index
   source
Log:
[e] (0) Visit the confessional. (credit: sb) (bug 6684)

Modified: index
===================================================================
--- index	2009-04-01 01:54:45 UTC (rev 2952)
+++ index	2009-04-01 18:21:44 UTC (rev 2953)
@@ -1875,6 +1875,19 @@
 
    </dd>
 
+   <dt>ECMAScript</dt>
+
+   <dd>
+
+    <p>Some parts of the language described by this specification only
+    support ECMAScript as the underlying scripting language. <a href=#refsECMAScript>[ECMAScript]</a></p>
+
+    <p class=note>The MIME type used to refer to ECMAScript in this
+    specification is <code title="">text/javascript</code>. This is a
+    willful violation of RFC 4329. <a href=#refsRFC4329>[RFC4329]</a></p>
+
+   </dd>
+
    <dt id=mq>Media Queries</dt>
 
    <dd>
@@ -4268,7 +4281,8 @@
   manner distinct from the precise technical meaning it is given in
   RFC 3986. Readers familiar with that RFC will find it easier to read
   <em>this</em> specification if they pretend the term "URL" as used
-  herein is really called something else altogether.</p>
+  herein is really called something else altogether. This is a willful
+  violation of RFC 3986. <a href=#refsRFC3986>RFC3986</a></p>
 
   </div>
 
@@ -4397,10 +4411,13 @@
 
   </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) --></div>
+  (earlier URI specs did) --><p class=note>These parsing rules are a willful violation of RFC
+  3986 and RFC 3987 to handle legacy content. <a href=#refsRFC3986>RFC3986</a> <a href=#refsRFC3987>RFC3987</a></p>
 
+  </div>
 
 
+
   <div class=impl>
 
   <h4 id=resolving-urls><span class=secno>2.5.3 </span>Resolving URLs</h4>
@@ -62890,6 +62907,7 @@
   Shanti Rao,
   Shaun Inman,
   Shiki Okasaka,
+  Sierk Bornemann,
   Sigbjørn Vik,
   Silvia Pfeiffer,
   Simon Montagu,

Modified: source
===================================================================
--- source	2009-04-01 01:54:45 UTC (rev 2952)
+++ source	2009-04-01 18:21:44 UTC (rev 2953)
@@ -911,6 +911,21 @@
 
    </dd>
 
+   <dt>ECMAScript</dt>
+
+   <dd>
+
+    <p>Some parts of the language described by this specification only
+    support ECMAScript as the underlying scripting language. <a
+    href="#refsECMAScript">[ECMAScript]</a></p>
+
+    <p class="note">The MIME type used to refer to ECMAScript in this
+    specification is <code title="">text/javascript</code>. This is a
+    willful violation of RFC 4329. <a
+    href="#refsRFC4329">[RFC4329]</a></p>
+
+   </dd>
+
    <dt id="mq">Media Queries</dt>
 
    <dd>
@@ -3871,7 +3886,8 @@
   manner distinct from the precise technical meaning it is given in
   RFC 3986. Readers familiar with that RFC will find it easier to read
   <em>this</em> specification if they pretend the term "URL" as used
-  herein is really called something else altogether.</p>
+  herein is really called something else altogether. This is a willful
+  violation of RFC 3986. <a href="#refsRFC3986">RFC3986</a></p>
 
   </div>
 
@@ -4018,6 +4034,11 @@
   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 willful violation of RFC
+  3986 and RFC 3987 to handle legacy content. <a
+  href="#refsRFC3986">RFC3986</a> <a
+  href="#refsRFC3987">RFC3987</a></p>
+
   </div>
 
 
@@ -73633,6 +73654,7 @@
   Shanti Rao,
   Shaun Inman,
   Shiki Okasaka,
+  Sierk Bornemann,
   Sigbjørn Vik,
   Silvia Pfeiffer,
   Simon Montagu,