[html5] r7493 - [giow] (3) Be more strict about what <script type=''> handling should look like. [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Oct 31 16:02:58 PDT 2012
Author: ianh
Date: 2012-10-31 16:02:57 -0700 (Wed, 31 Oct 2012)
New Revision: 7493
Modified:
complete.html
index
source
Log:
[giow] (3) Be more strict about what <script type=''> handling should look like.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=16887
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2012-10-30 22:30:24 UTC (rev 7492)
+++ complete.html 2012-10-31 23:02:57 UTC (rev 7493)
@@ -248,7 +248,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 30 October 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 31 October 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -16112,7 +16112,7 @@
<div class=impl>
- <!-- this paragraph is also present in the <script> section -->
+ <!-- similar paragraph is also present in the <script> section -->
<p>When examining types to determine if they support the language,
user agents must not ignore unknown MIME parameters — types
with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
@@ -17414,14 +17414,14 @@
<div class=impl>
- <p>A user agent is said to <dfn id=support-the-scripting-language>support the scripting language</dfn>
- if <var><a href="#the-script-block's-type">the script block's type</a></var> is an <a href=#ascii-case-insensitive>ASCII
- case-insensitive</a> match for the <a href=#mime-type>MIME type</a> string
- of a scripting language that the user agent implements.</p>
+ <p>A user agent is said to <dfn id=support-the-scripting-language>support the scripting language</dfn> if each component of <var><a href="#the-script-block's-type">the
+ script block's type</a></var> is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the corresponding
+ component in the <a href=#mime-type>MIME type</a> string of a scripting language that the user agent
+ implements.</p>
</div>
- <p>The following lists some <a href=#mime-type>MIME type</a> strings and the
+ <p>The following lists the <a href=#mime-type>MIME type</a> strings that user agents must recognize, and the
languages to which they refer:</p>
<dl><dt>"<code>application/ecmascript</code>"</dt>
@@ -17447,10 +17447,11 @@
</dl><div class=impl>
- <p>User agents may support other <a href=#mime-type title="MIME type">MIME
- types</a> and other languages.</p>
+ <p>User agents may support other <a href=#mime-type title="MIME type">MIME types</a> for other languages,
+ but must not support other <a href=#mime-type title="MIME type">MIME types</a> for the languages in the list
+ above. User agents are not required to support the languages listed above.</p>
- <p>The following <a href=#mime-type title="MIME type">MIME types</a> must not
+ <p>The following <a href=#mime-type title="MIME type">MIME types</a> (with or without parameters) must not
be interpreted as scripting languages:</p>
<ul class=brief><li>"<code>text/plain</code>"
@@ -17471,13 +17472,16 @@
formats for data blocks, and it would be problematic if they were
suddenly to be interpreted as script by a user agent.</p>
- <!-- this paragraph is also present in the <style> section -->
- <p>When examining types to determine if they support the language,
- user agents must not ignore unknown MIME parameters — types
- with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
- parameter for the purpose of comparing <a href=#mime-type title="MIME type">MIME
- types</a> here.</p>
+ <!-- a similar paragraph is also present in the <style> section -->
+ <p>When examining types to determine if they represent supported languages, user agents must not
+ ignore MIME parameters. Types are to be compared including all parameters.</p> <!-- whether the
+ order of parameters matters is left undefined until such time as it matters; so far the only
+ relevant parameter is 'e4x' -->
+
+ <p class=note>For example, types that include the <code title="">charset</code> parameter will
+ not be recognized as referencing any of the scripting languages listed above.</p>
+
</div>
Modified: index
===================================================================
--- index 2012-10-30 22:30:24 UTC (rev 7492)
+++ index 2012-10-31 23:02:57 UTC (rev 7493)
@@ -248,7 +248,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 30 October 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 31 October 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -16112,7 +16112,7 @@
<div class=impl>
- <!-- this paragraph is also present in the <script> section -->
+ <!-- similar paragraph is also present in the <script> section -->
<p>When examining types to determine if they support the language,
user agents must not ignore unknown MIME parameters — types
with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
@@ -17414,14 +17414,14 @@
<div class=impl>
- <p>A user agent is said to <dfn id=support-the-scripting-language>support the scripting language</dfn>
- if <var><a href="#the-script-block's-type">the script block's type</a></var> is an <a href=#ascii-case-insensitive>ASCII
- case-insensitive</a> match for the <a href=#mime-type>MIME type</a> string
- of a scripting language that the user agent implements.</p>
+ <p>A user agent is said to <dfn id=support-the-scripting-language>support the scripting language</dfn> if each component of <var><a href="#the-script-block's-type">the
+ script block's type</a></var> is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for the corresponding
+ component in the <a href=#mime-type>MIME type</a> string of a scripting language that the user agent
+ implements.</p>
</div>
- <p>The following lists some <a href=#mime-type>MIME type</a> strings and the
+ <p>The following lists the <a href=#mime-type>MIME type</a> strings that user agents must recognize, and the
languages to which they refer:</p>
<dl><dt>"<code>application/ecmascript</code>"</dt>
@@ -17447,10 +17447,11 @@
</dl><div class=impl>
- <p>User agents may support other <a href=#mime-type title="MIME type">MIME
- types</a> and other languages.</p>
+ <p>User agents may support other <a href=#mime-type title="MIME type">MIME types</a> for other languages,
+ but must not support other <a href=#mime-type title="MIME type">MIME types</a> for the languages in the list
+ above. User agents are not required to support the languages listed above.</p>
- <p>The following <a href=#mime-type title="MIME type">MIME types</a> must not
+ <p>The following <a href=#mime-type title="MIME type">MIME types</a> (with or without parameters) must not
be interpreted as scripting languages:</p>
<ul class=brief><li>"<code>text/plain</code>"
@@ -17471,13 +17472,16 @@
formats for data blocks, and it would be problematic if they were
suddenly to be interpreted as script by a user agent.</p>
- <!-- this paragraph is also present in the <style> section -->
- <p>When examining types to determine if they support the language,
- user agents must not ignore unknown MIME parameters — types
- with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
- parameter for the purpose of comparing <a href=#mime-type title="MIME type">MIME
- types</a> here.</p>
+ <!-- a similar paragraph is also present in the <style> section -->
+ <p>When examining types to determine if they represent supported languages, user agents must not
+ ignore MIME parameters. Types are to be compared including all parameters.</p> <!-- whether the
+ order of parameters matters is left undefined until such time as it matters; so far the only
+ relevant parameter is 'e4x' -->
+
+ <p class=note>For example, types that include the <code title="">charset</code> parameter will
+ not be recognized as referencing any of the scripting languages listed above.</p>
+
</div>
Modified: source
===================================================================
--- source 2012-10-30 22:30:24 UTC (rev 7492)
+++ source 2012-10-31 23:02:57 UTC (rev 7493)
@@ -17183,7 +17183,7 @@
<div class="impl">
- <!-- this paragraph is also present in the <script> section -->
+ <!-- similar paragraph is also present in the <script> section -->
<p>When examining types to determine if they support the language,
user agents must not ignore unknown MIME parameters — types
with unknown parameters must be assumed to be unsupported. The <code
@@ -18662,14 +18662,14 @@
<div class="impl">
- <p>A user agent is said to <dfn>support the scripting language</dfn>
- if <var>the script block's type</var> is an <span>ASCII
- case-insensitive</span> match for the <span>MIME type</span> string
- of a scripting language that the user agent implements.</p>
+ <p>A user agent is said to <dfn>support the scripting language</dfn> if each component of <var>the
+ script block's type</var> is an <span>ASCII case-insensitive</span> match for the corresponding
+ component in the <span>MIME type</span> string of a scripting language that the user agent
+ implements.</p>
</div>
- <p>The following lists some <span>MIME type</span> strings and the
+ <p>The following lists the <span>MIME type</span> strings that user agents must recognize, and the
languages to which they refer:</p>
<dl>
@@ -18699,10 +18699,11 @@
<div class="impl">
- <p>User agents may support other <span title="MIME type">MIME
- types</span> and other languages.</p>
+ <p>User agents may support other <span title="MIME type">MIME types</span> for other languages,
+ but must not support other <span title="MIME type">MIME types</span> for the languages in the list
+ above. User agents are not required to support the languages listed above.</p>
- <p>The following <span title="MIME type">MIME types</span> must not
+ <p>The following <span title="MIME type">MIME types</span> (with or without parameters) must not
be interpreted as scripting languages:</p>
<ul class="brief">
@@ -18727,14 +18728,16 @@
formats for data blocks, and it would be problematic if they were
suddenly to be interpreted as script by a user agent.</p>
- <!-- this paragraph is also present in the <style> section -->
- <p>When examining types to determine if they support the language,
- user agents must not ignore unknown MIME parameters — types
- with unknown parameters must be assumed to be unsupported. The <code
- title="">charset</code> parameter must be treated as an unknown
- parameter for the purpose of comparing <span title="MIME type">MIME
- types</span> here.</p>
+ <!-- a similar paragraph is also present in the <style> section -->
+ <p>When examining types to determine if they represent supported languages, user agents must not
+ ignore MIME parameters. Types are to be compared including all parameters.</p> <!-- whether the
+ order of parameters matters is left undefined until such time as it matters; so far the only
+ relevant parameter is 'e4x' -->
+
+ <p class="note">For example, types that include the <code title="">charset</code> parameter will
+ not be recognized as referencing any of the scripting languages listed above.</p>
+
</div>
More information about the Commit-Watchers
mailing list