HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2812[Conformance Checkers] [Gecko] [Internet Explorer] [Opera] [Webkit] [Tools] Trade willful violation of ECMAScript for unintentional violation of Unicode - update the character encoding alias rules.2009-02-13 03:21
@@ -40228,20 +40228,23 @@ interface <dfn>Window</dfn> {
     <p>A <span>browsing context</span> that is assigned responsibility
     for actions taken by the script.</p>
 
     <p class="example">When a script creates and <span
     title="navigate">navigates</span> a new <span>top-level browsing
     context</span>, the <code title="dom-opener">opener</code>
     attribute of the new <span>browsing context</span>'s
     <code>Window</code> object will be set to the <span>script's
     browsing context</span>'s <code>Window</code> object.</p>
 
+    <p class="note">This is a willful violation of ECMAScript edition
+    3. <a href="#refsECMA262">[ECMA262]</a></p>
+
    </dd>
 
    <dt>A <dfn title="script's character encoding">character encoding</dfn></dt>
 
    <dd>
 
     <p>A character encoding, set when the script is created, used to
     encode URLs.  <span id="sce-not-copy">If the character encoding is
     set from another source, e.g. a <span>document's character
     encoding</span>, then the <span>script's character encoding</span>
@@ -55282,25 +55285,24 @@ interface <dfn>MessageChannel</dfn> {
   should support all the IANA-registered aliases. <a
   href="#refsIANACHARSET">[IANACHARSET]</a></p>
 
   <!-- XXX should all this be abstracted out so it can be used for
   <script charset=""> and <form accept-charset="">? Maybe move this
   stuff and the 'character encodings' section of the terminology
   section into its own infrastructure subsection? -->
 
   <p>When comparing a string specifying a character encoding with the
   name or alias of a character encoding to determine if they are
-  equal, user agents must ignore all characters in the ranges U+0009
-  to U+000D, U+0020 to U+002F, U+003A to U+0040, U+005B to U+0060, and
-  U+007B to U+007E (all whitespace and punctuation characters in
-  ASCII) in both names, and then perform the comparison in an
-  <span>ASCII case-insensitive</span> manner.</p>
+  equal, user agents must use the Charset Alias Matching rules defined
+  in Unicode Technical Standard #22. <a
+  href="#refsUTS22">[UTS22]</a></p> <!-- XXXrefs
+  http://unicode.org/reports/tr22/#Charset_Alias_Matching -->
 
   <p class="example">For instance, "GB_2312-80" and "g.b.2312(80)" are
   considered equivalent names.</p>
 
   <p>When a user agent would otherwise use an encoding given in the
   first column of the following table, it must instead use the
   encoding given in the cell in the second column of the same row. Any
   bytes that are treated differently due to this encoding aliasing
   must be considered <span title="parse error">parse
   errors</span>.</p>

|