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

html5/webstorage Overview.html,1.33,1.34

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 29 Apr 2009 08:02:52 +0000
To: public-html-commits@w3.org
Message-Id: <E1Lz4km-0000k4-4i@lionel-hutz.w3.org>
Update of /sources/public/html5/webstorage
In directory hutz:/tmp/cvs-serv2838

Modified Files:
	Overview.html 
Log Message:
Define the task sources used for WebStorage; define that 'storage' events are queued not synchronous. (Also: Add some v4 notes for <canvas>.) (whatwg r3025)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- Overview.html	29 Apr 2009 05:06:59 -0000	1.33
+++ Overview.html	29 Apr 2009 08:02:49 -0000	1.34
@@ -534,12 +534,14 @@
   is fired when a storage area changes, as described in the previous
   two sections (<a href="#sessionStorageEvent">for session
   storage</a>, <a href="#localStorageEvent">for local
-  storage</a>).<p>When this happens, the user agent must dispatch an event with the
-  name <code><a href="#storage-0">storage</a></code>, with no namespace, which does not bubble
-  and is not cancelable, and which uses the <code><a href="#storageevent">StorageEvent</a></code>
-  interface, at each <code>Window</code> object whose
-  <code>Document</code> object both has a <code><a href="#storage-0">Storage</a></code> object
-  that is affected, and is <span>fully active</span>.<p>If the event is being fired due to an invocation of the
+  storage</a>).<p>When this happens, the user agent must <span>queue a task</span>
+  to fire an event with the name <code><a href="#storage-0">storage</a></code>, with no
+  namespace, which does not bubble and is not cancelable, and which
+  uses the <code><a href="#storageevent">StorageEvent</a></code> interface, at each
+  <code>Window</code> object whose <code>Document</code> object both
+  has a <code><a href="#storage-0">Storage</a></code> object that is affected, and is
+  <span>fully active</span>.<p>The <span>task source</span> for this task is the <span>DOM
+  manipulation task source</span>.<p>If the event is being fired due to an invocation of the
   <code title="dom-Storage-setItem"><a href="#dom-storage-setitem">setItem()</a></code> or <code title="dom-Storage-removeItem"><a href="#dom-storage-removeitem">removeItem()</a></code> methods, the
   event must have its <code title="dom-StorageEvent-key"><a href="#dom-storageevent-key">key</a></code>
   attribute set to the name of the key in question, its <code title="dom-StorageEvent-oldValue"><a href="#dom-storageevent-oldvalue">oldValue</a></code> attribute set to
@@ -938,7 +940,8 @@
    transaction. Rollback the transaction. Any still-pending statements
    in the transaction are discarded.</li>
 
-  </ol><h3 id="synchronous-database-api"><span class="secno">4.5 </span>Synchronous database API</h3><pre class="idl">interface <dfn id="databasesync">DatabaseSync</dfn> {
+  </ol><p>The <span>task source</span> for these tasks is the <dfn id="database-access-task-source">database
+  access task source</dfn>.<h3 id="synchronous-database-api"><span class="secno">4.5 </span>Synchronous database API</h3><pre class="idl">interface <dfn id="databasesync">DatabaseSync</dfn> {
   <a href="#sqltransactionsync">SQLTransactionSync</a> <a href="#dom-database-sync-transaction" title="dom-database-sync-transaction">transaction</a>();
   <a href="#sqltransactionsync">SQLTransactionSync</a> <a href="#dom-database-sync-readtransaction" title="dom-database-sync-readTransaction">readTransaction</a>();
 
Received on Wednesday, 29 April 2009 08:03:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 April 2009 08:03:02 GMT