hixie: Define some types that are never going to be scripting types and are therefore always going to be 'safe' to use as data format types in <script> (even though in practice authors really should be using more specific types). (whatwg r6212)

hixie: Define some types that are never going to be scripting types and
are therefore always going to be 'safe' to use as data format types in
<script> (even though in practice authors really should be using more
specific types). (whatwg r6212)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4977&r2=1.4978&f=h
http://html5.org/tools/web-apps-tracker?from=6211&to=6212

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4977
retrieving revision 1.4978
diff -u -d -r1.4977 -r1.4978
--- Overview.html 10 Jun 2011 20:38:08 -0000 1.4977
+++ Overview.html 10 Jun 2011 22:43:17 -0000 1.4978
@@ -13766,6 +13766,23 @@
   <p>User agents may support other <a href="#mime-type" title="MIME type">MIME
   types</a> and other languages.</p>
 
+  <p>The following <a href="#mime-type" title="MIME type">MIME types</a> must not
+  be interpreted as scripting languages:</p>
+
+  <ul class="brief"><li>"<code>text/plain</code>"
+   <li>"<code>text/xml</code>"
+   
+   <li>"<code>application/octet-stream</code>"
+   <li>"<code>application/xml</code>"
+   
+   
+
+   
+  </ul><p class="note">These types are explicitly listed here because they
+  are poorly-defined types that are nonetheless likely to be used as
+  formats for data blocks, and it would be problematic if they were
+  suddenly to be interpreted as script by a user agent.</p>
+
   
   <p>When examining types to determine if they support the language,
   user agents must not ignore unknown MIME parameters &mdash; types

Received on Friday, 17 June 2011 09:53:22 UTC