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

spec/Overview.html 1.2118 2954 Refer to ECMAScript as JavaScript more c

From: poot <cvsmail@w3.org>
Date: Thu, 2 Apr 2009 12:36:31 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090402033631.B717C2BC34@toro.w3.mag.keio.ac.jp>
Refer to ECMAScript as JavaScript more consistently; add the various
MIME types that JavaScript is sometimes known as. (whatwg r2954)

rules for parsing floating point number values
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#rules-for-parsing-floating-point-number-values
4.10.4.2.7 The maxlength attribute
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#the-maxlength-attribute
Editor's Draft 2 April 2009
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#editor-s-draft-date-1-january-1970
best representation of the floating point number
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#best-representation-of-the-floating-point-number
The element containing the character encoding declaration must be serialised completely within the first 512 bytes of the document.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#charset512
2.4.4.3 Real numbers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#real-numbers
content attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#content-attributes
Event handler DOM attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#event-handler-dom-attributes
3.7.1 Controlling the input stream
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#controlling-the-input-stream
4.10.4.2.8 The pattern attribute
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#the-pattern-attribute
2.2.1 Dependencies
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#dependencies
Event handler content attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#event-handler-content-attributes
DOM attributes
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#dom-attributes
Status of this document
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#status-of-this-document
A vocabulary and associated APIs for HTML and XHTML
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#a-vocabulary-and-associated-apis-for-html-and-xhtml
setTimeout(handler, timeout[, arguments...])
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#dom-windowtimers-settimeout
registerContentHandler()
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#dom-navigator-registercontenthandler
support the scripting language
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#support-the-scripting-language
RowSpecification
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#rowspecification
Media Queries
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#mq
script's global object
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#script-s-global-object
5.5.6.5 Runtime script errors
http://people.w3.org/mike/diffs/html5/spec/Overview.1.2118.html#runtime-script-errors

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2117&r2=1.2118&f=h
http://html5.org/tools/web-apps-tracker?from=2953&to=2954

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2117
retrieving revision 1.2118
diff -u -d -r1.2117 -r1.2118
--- Overview.html	1 Apr 2009 21:26:18 -0000	1.2117
+++ Overview.html	2 Apr 2009 00:48:59 -0000	1.2118
@@ -146,7 +146,7 @@
    <p><a href=http://www.w3.org/><img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72></a></p>
    <h1>HTML 5</h1>
    <h2 class="no-num no-toc" id=a-vocabulary-and-associated-apis-for-html-and-xhtml>A vocabulary and associated APIs for HTML and XHTML</h2>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-1-january-1970><!--ZZZ: W3C Working Draft 12 February 2009 <!-- fix date ZZZ --><!----> Editor's Draft 1 April 2009 <!--:ZZZ--></h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-1-january-1970><!--ZZZ: W3C Working Draft 12 February 2009 <!-- fix date ZZZ --><!----> Editor's Draft 2 April 2009 <!--:ZZZ--></h2>
    <dl><!-- ZZZ: update the month/day (twice), uncomment out 
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2009/WD-html5-20090212/">http://www.w3.org/TR/2009/WD-html5-20090212/</a></dd>
@@ -237,7 +237,7 @@
   track.
   <!--ZZZ:-->
   <!-- This specification is the 12 February 2009 Working Draft. -->
-  This specification is the 1 April 2009 Editor's Draft.
+  This specification is the 2 April 2009 Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href=http://www.whatwg.org/>WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -1281,7 +1281,7 @@
   being referred to, they are referred to as <dfn id=content-attributes>content
   attributes</dfn> for HTML and XML attributes, and <dfn id=dom-attributes>DOM
   attributes</dfn> for those from the DOM. Similarly, the term
-  "properties" is used for both ECMAScript object properties and CSS
+  "properties" is used for both JavaScript object properties and CSS
   properties. When these are ambiguous they are qualified as object
   properties and CSS properties respectively.<p>The term <a href=#html-documents>HTML documents</a> is sometimes used in
   contrast with <a href=#xml-documents>XML documents</a> to specifically mean
@@ -1689,16 +1689,18 @@
 
    </dd>
 
-   <dt>ECMAScript</dt>
+   <dt>JavaScript</dt>
 
    <dd>
 
     <p>Some parts of the language described by this specification only
-    support ECMAScript as the underlying scripting language. <a href=#references>[ECMAScript]</a></p>
+    support JavaScript as the underlying scripting language. <a href=#references>[ECMA262]</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=#references>[RFC4329]</a></p>
+    <p class=note>The term "JavaScript" is used to refer to ECMA262,
+    rather than the official term ECMAScript, since the term
+    JavaScript is more widely known. Similarly, the MIME type used to
+    refer to JavaScript in this specification is <code title="">text/javascript</code>, since that is the most commonly
+    used type. This is a willful violation of RFC 4329. <a href=#references>[RFC4329]</a></p>
 
    </dd>
 
@@ -1711,12 +1713,12 @@
 
    </dd>
 
-  </dl><p>This specification does not require support of any particular
-  network transport protocols, style sheet language, scripting
-  language, or any of the DOM and WebAPI specifications beyond those
-  described above. However, the language described by this
-  specification is biased towards CSS as the styling language,
-  ECMAScript as the scripting language, and HTTP as the network
+  </dl><p>This specification does not <em>require</em> support of any
+  particular network transport protocols, style sheet language,
+  scripting language, or any of the DOM and WebAPI specifications
+  beyond those described above. However, the language described by
+  this specification is biased towards CSS as the styling language,
+  JavsScript as the scripting language, and HTTP as the network
   protocol, and several features assume that those languages and
   protocols are in use.</p>
 
@@ -2076,7 +2078,7 @@
 
   <p>The <dfn id=best-representation-of-the-floating-point-number>best representation of the floating point number</dfn>
   <var title="">n</var> is the string obtained from applying the
-  ECMAScript operator ToString to <var title="">n</var>.</p>
+  JavaScript operator ToString to <var title="">n</var>.</p>
 
   <p>The <dfn id=rules-for-parsing-floating-point-number-values>rules for parsing floating point number values</dfn> are
   as given in the following algorithm. As with the previous
@@ -7988,7 +7990,7 @@
    <code><a href=#navigator>Navigator</a></code>, and <code><a href=#selection-0>Selection</a></code> objects, the
    various <code><a href=#barprop>BarProp</a></code> objects, the two <code>Storage</code>
    objects, and the various <code><a href=#htmlcollection-0>HTMLCollection</a></code> objects. It
-   also includes all the WebIDL prototypes in the ECMAScript binding,
+   also includes all the WebIDL prototypes in the JavaScript binding,
    including the <code>Document</code> object's prototype.)</li>
 
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E...%3Ciframe%20src%3D%22document%22%3E%3C%2Fiframe%3E%0A%3Cscript%3Eonload%20%3D%20function%20()%20%7B%20f%20%3D%20document.getElementsByTagName('iframe')%5B0%5D%3B%20d%20%3D%20f.contentWindow.document%3B%20%7D%3C%2Fscript%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22w(d.documentElement.innerHTML)%22%20value%3D%22dump%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cscript%3Evar%20x%20%3D%20new%20XMLHttpRequest()%3Bx.open(%26quot%3BGET%26quot%3B%2C%20%26quot%3BGET%26quot%3B)%3Bx.onreadystatechange%3Dfunction()%20%7B%20alert(x.readyState)%3B%20%7D%3Bx.send(null)%3B%3C%2Fscript%3E')%3Bd.close()%3B%20setTimeout(function()%20%7B%20d.open()%3B%20d.write('%3Cp%3Etest%3C%2Fp%3E')%3B%20d.close()%20%7D%2C%200)%3B%22%20value%3D%22xhr%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.onclick%20%3D%20function()%20%7B%20w('click')%20%7D%22%20value%3D%22add%20click%20handler%22%3E%0A%3Cinput%20type%3Dbutton%20oncick%3D%22d.open()%3B%20d.write('%3Cp%3Etest%3C%2Fp%3E')%3B%20d.close()%22%20value%3D%22replace%22%3E%0A%3Cinput%20type%3Dbutton%20onclick%3D%22d.open()%3B%20d.write('%3Cp%3E%3Cscript%3Ei%20%3D%200%3B%20setTimeout(%26quot%3Bparent.w(i%2B%2B)%26quot%3B%2C%202000)%3C%2Fscript%3E%3C%2Fp%3E')%3B%20d.close()%22%20value%3D%22replace%20with%20timer%22%3E -->
@@ -9491,7 +9493,7 @@
    bytes of the document.</li>
 
    <li>There can only be one character encoding declaration in the
-   document. <!-- conformance critiera for this one are given in
+   document.</li> <!-- conformance critiera for this one are given in
    the XML spec, the <meta> section just after defining charset="",
    and the character encoding pragma section. And actually this
    statement isn't quite true, since you can have an XML one and an
@@ -10261,14 +10263,26 @@
   scripting language that the user agent implements.</p>
 
   </div><p>The following lists some MIME types and the languages to which
-  they refer:<dl><dt><code>text/javascript</code></dt>
+  they refer:<dl><dt><code>application/ecmascript</code></dt>
+   <dt><code>application/javascript</code></dt>
+   <dt><code>application/x-ecmascript</code></dt>
+   <dt><code>application/x-javascript</code></dt>
+   <dt><code>text/ecmascript</code></dt>
+   <dt><code>text/javascript</code></dt>
+   <dt><code>text/javascript1.0</code></dt>
    <dt><code>text/javascript1.1</code></dt>
    <dt><code>text/javascript1.2</code></dt>
    <dt><code>text/javascript1.3</code></dt>
-   <dd>ECMAScript. <a href=#references>[ECMA262]</a></dd>
+   <dt><code>text/javascript1.4</code></dt>
+   <dt><code>text/javascript1.5</code></dt>
+   <dt><code>text/jscript</code></dt>
+   <dt><code>text/livescript</code></dt>
+   <dt><code>text/x-ecmascript</code></dt>
+   <dt><code>text/x-javascript</code></dt>
+   <dd>JavaScript. <a href=#references>[ECMA262]</a></dd>
 
    <dt><code>text/javascript;e4x=1</code></dt>
-   <dd>ECMAScript with ECMAScript for XML. <a href=#references>[ECMA357]</a></dd>
+   <dd>JavaScript with ECMAScript for XML. <a href=#references>[ECMA357]</a></dd>
 
   </dl><div class=impl>
 
@@ -28283,19 +28297,20 @@
   attribute must be equal to or less than the element's <a href=#maximum-allowed-value-length>maximum
   allowed value length</a>.<h6 id=the-pattern-attribute><span class=secno>4.10.4.2.8 </span>The <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code> attribute</h6><p>The <dfn id=attr-input-pattern title=attr-input-pattern><code>pattern</code></dfn>
   attribute specifies a regular expression against which the control's
-  <a href=#concept-fe-value title=concept-fe-value>value</a> is to be checked.<p>If specified, the attribute's value must match the <i title="">Pattern</i> production of ECMA 262's grammar. <a href=#references>[ECMA262]</a><div class=impl>
+  <a href=#concept-fe-value title=concept-fe-value>value</a> is to be checked.<p>If specified, the attribute's value must match the JavaScript <i title="">Pattern</i> production. <a href=#references>[ECMA262]</a><div class=impl>
 
   <p><strong>Constraint validation:</strong> If the element's <a href=#concept-fe-value title=concept-fe-value>value</a> is not the empty string, and
   the element's <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code>
-  attribute is specified and the attribute's value, when compiled as
-  an ECMA 262 regular expression with the <code title="">global</code>, <code title="">ignoreCase</code>, and <code title="">multiline</code> flags <em>disabled</em> (see ECMA 262,
-  sections 15.10.7.2 through 15.10.7.4), compiles successfully but the
-  resulting regular expression does not match the entirety of the
-  element's <a href=#concept-fe-value title=concept-fe-value>value</a>, then the
-  element is <a href=#suffering-from-a-pattern-mismatch>suffering from a pattern mismatch</a>. <a href=#references>[ECMA262]</a></p>
+  attribute is specified and the attribute's value, when compiled as a
+  JavaScript regular expression with the <code title="">global</code>,
+  <code title="">ignoreCase</code>, and <code title="">multiline</code> flags <em>disabled</em> (see ECMA262
+  Edition 3, sections 15.10.7.2 through 15.10.7.4), compiles
+  successfully but the resulting regular expression does not match the
+  entirety of the element's <a href=#concept-fe-value title=concept-fe-value>value</a>, then the element is
+  <a href=#suffering-from-a-pattern-mismatch>suffering from a pattern mismatch</a>. <a href=#references>[ECMA262]</a></p>
 
   <p class=note>This implies that the regular expression language
-  used for this attribute is the same as that defined in ECMA 262,
+  used for this attribute is the same as that used in JavaScript,
   except that the <code title=attr-input-pattern><a href=#attr-input-pattern>pattern</a></code>
   attribute must match the entire value, not just any subset (somewhat
   as if it implied a <code title="">^(?:</code> at the start of the
@@ -31444,7 +31459,7 @@
   // binding-specific interface
 };</pre>
 
-  <p>In ECMAScript, two classes of objects are said to implement this
+  <p>In JavaScript, two classes of objects are said to implement this
   interface: Numbers representing non-negative integers, and
   homogeneous arrays of Numbers representing non-negative
   integers. Thus, <code>[1,0,9]</code> is a
@@ -31454,11 +31469,11 @@
   an integer.</p>
 
   <p>User agents must always represent <code><a href=#rowspecification>RowSpecification</a></code>s
-  in ECMAScript by using arrays, even if the path only has one
+  in JavaScript by using arrays, even if the path only has one
   number.</p>
 
   <p>The root of the tree is represented by the empty path; in
-  ECMAScript, this is the empty array (<code>[]</code>). Only the
+  JavaScript, this is the empty array (<code>[]</code>). Only the
   <code title=dom-provider-getRowCount><a href=#dom-provider-getrowcount>getRowCount()</a></code> and
   <code title=dom-provider-getChildAtPosition><a href=#dom-provider-getchildatposition>GetChildAtPosition()</a></code>
   methods ever get called with the empty path.</p>
@@ -35909,12 +35924,12 @@
     environment.</p>
 
     <p>If the <a href=#script-s-global-object>script's global object</a> is a
-    <code><a href=#window>Window</a></code> object, then in JavaScript, the <code title="">this</code> keyword in the global scope must, contrary to
-    the ECMAScript specification, return the <code><a href=#window>Window</a></code>
-    object's <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+    <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 willful violation of ECMAScript edition
-    3. <a href=#references>[ECMA262]</a></p>
+    <p class=note>This is a willful violation of the JavaScript
+    specification current at the time of writing (ECMAScript edition
+    3). <a href=#references>[ECMA262]</a></p>
 
    </dd>
 
@@ -36431,7 +36446,7 @@
   <code><a href=#messageport>MessagePort</a></code> objects.</p>
 
   <hr></div><p><dfn id=event-handler-content-attributes>Event handler content attributes</dfn>, when specified, must
-  contain valid ECMAScript code matching the ECMAScript <code title="">FunctionBody</code> production. <a href=#references>[ECMA262]</a><div class=impl>
+  contain valid JavaScript code matching the <code title="">FunctionBody</code> production. <a href=#references>[ECMA262]</a><div class=impl>
 
   <!-- SCRIPT EXEC -->
   <p>When an event handler content attribute is set, if the element is
@@ -36724,7 +36739,7 @@
   <h5 id=runtime-script-errors><span class=secno>5.5.6.5 </span>Runtime script errors</h5>
 
   <p><em>This section only applies to user agents that support
-  scripting in general and ECMAScript in particular.</em></p>
+  scripting in general and JavaScript in particular.</em></p>
 
   <p>Whenever a runtime script error occurs in one of the scripts
   associated with a <code>Document</code>, the user agent must
@@ -37404,7 +37419,7 @@
 
   <p>User agents must not raise any other exceptions (other than
   binding-specific exceptions, such as for an incorrect number of
-  arguments in an ECMAScript implementation).</p>
+  arguments in an JavaScript implementation).</p>
 
   <p>This section does not define how the pages registered by these
   methods are used, beyond the requirements on how to process the <var title="">url</var> value (see above). To some extent, the <a href=#navigate title=navigate>processing model for navigating across
@@ -56853,7 +56868,7 @@
   object. <span class=XXX>define the actual requirements for
   this method, as with the previous one.</span> That string must be
   parsed using the specified <var title="">language</var> (defaulting
-  to ECMAScript if the third argument is omitted) and executed in the
+  to JavaScript if the third argument is omitted) and executed in the
   scope of the <a href=#browsing-context>browsing context</a> associated with the
   <code><a href=#window>Window</a></code> object on which the <code title=setTimeout>setTimeout()</code> method was invoked.<p class=XXX>Need to define <var title="">language</var> values;
   need to define that the <a href=#concept-script title=concept-script>script</a>
Received on Thursday, 2 April 2009 03:37:10 GMT

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