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

webstorage/Overview.html 1.17 2954 Refer to ECMAScript as JavaScript mo

From: poot <cvsmail@w3.org>
Date: Thu, 2 Apr 2009 12:35:31 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090402033531.80E9D2BC69@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)

7.4 SQL and user agents
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#sql-and-user-agents
7.5 SQL injection
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#sql-injection
Status of this document
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#status-of-this-document
3 Storing name/value pairs
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#storage
item(index)
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#dom-sqlresultsetrowlist-item
References
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#references
Editor's Draft 2 April 2009
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#editor-s-draft-date-zzz-9-june-2008
2 Terminology
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.17.html#terminology

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

===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- Overview.html	27 Mar 2009 01:09:31 -0000	1.16
+++ Overview.html	2 Apr 2009 00:49:12 -0000	1.17
@@ -145,7 +145,7 @@
   </style><link href=http://www.w3.org/StyleSheets/TR/%57%33%43-ED rel=stylesheet type=text/css><!-- ZZZ ED vs WD --><div class=head>
    <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>Web Storage</h1>
-   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->27 March 2009</h2>
+   <h2 class="no-num no-toc" id=editor-s-draft-date-zzz-9-june-2008><!-- "W3C Working Draft" --> Editor's Draft <!--ZZZ-->2 April 2009</h2>
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2009/WD-webstorage-20090101/">http://www.w3.org/TR/2009/WD-webstorage-20090101/</a></dd>
@@ -202,7 +202,7 @@
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
   <!--ZZZ:-->
-  This specification is the 27 March 2009 <!--ZZZ "Working Draft"-->Editor's Draft.
+  This specification is the 2 April 2009 <!--ZZZ "Working Draft"-->Editor's Draft.
   <!--:ZZZ-->
   </p><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href=http://www.w3.org/Consortium/Patent-Policy-20040205/>5
   February 2004 W3C Patent Policy</a>. W3C maintains a <a href=http://www.w3.org/2004/01/pp-impl/42538/status rel=disclosure>public list of
@@ -297,7 +297,9 @@
   <code>Node</code> objects as defined in the DOM Core
   specifications. <a href=#refsDOM3CORE>[DOM3CORE]</a><p>A DOM attribute is said to be <em>getting</em> when its value is
   being retrieved (e.g. by author script), and is said to be
-  <em>setting</em> when a new value is assigned to it.<h2 id=storage><span class=secno>3 </span>Storing name/value pairs</h2><h3 id=introduction><span class=secno>3.1 </span>Introduction</h3><p><em>This section is non-normative.</em><p>This specification introduces two related mechanisms, similar to
+  <em>setting</em> when a new value is assigned to it.<p>The term "JavaScript" is used to refer to ECMA262, rather than
+  the official term ECMAScript, since the term JavaScript is more
+  widely known. <a href=#refsECMA262>[ECMA262]</a><h2 id=storage><span class=secno>3 </span>Storing name/value pairs</h2><h3 id=introduction><span class=secno>3.1 </span>Introduction</h3><p><em>This section is non-normative.</em><p>This specification introduces two related mechanisms, similar to
   HTTP session cookies, for storing structured data on the client
   side. <a href=#refsRFC2109>[RFC2109]</a> <a href=#refsRFC2965>[RFC2965]</a><p>The first is designed for scenarios where the user is carrying
   out a single transaction, but could be carrying out multiple
@@ -796,7 +798,7 @@
   with the given index <var title="">index</var>. If there is no such
   row, then the method must raise an <code>INDEX_SIZE_ERR</code>
   exception.<p>Each row must be represented by a native ordered dictionary data
-  type. In the ECMAScript binding, this must be <code>Object</code>.
+  type. In the JavaScript binding, this must be <code>Object</code>.
   Each row object must have one property (or dictionary entry) per
   column, with those properties enumerating in the order that these
   columns were returned by the database. Each property must have the
@@ -1130,6 +1132,6 @@
   features that control how databases are stored on disk. For example,
   there is little reason to allow Web authors to control the character
   encoding used in the disk representation of the data, as all data in
-  ECMAScript is implicitly UTF-16.<h3 id=sql-injection><span class=secno>7.5 </span>SQL injection</h3><p>Authors are strongly recommended to make use of the <code title="">?</code> placeholder feature of the <code title=dom-sqltransaction-executeSql><a href=#dom-sqltransaction-executesql>executeSql()</a></code> method,
+  JavaScript is implicitly UTF-16.<h3 id=sql-injection><span class=secno>7.5 </span>SQL injection</h3><p>Authors are strongly recommended to make use of the <code title="">?</code> placeholder feature of the <code title=dom-sqltransaction-executeSql><a href=#dom-sqltransaction-executesql>executeSql()</a></code> method,
   and to never construct SQL statements on the fly.<h2 class=no-num id=references>References</h2><p class=big-issue>This section will be written in a future
   draft.<!--XXX-->
Received on Thursday, 2 April 2009 03:36:13 GMT

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