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

Mention that tasks from discarded documents are also discarded. Change some prose to mention origins and sites instead of domains. Fire 'storage' on inactive documents as well so they all get notified. (whatwg r3026)

From: poot <cvsmail@w3.org>
Date: Wed, 29 Apr 2009 17:36:11 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090429083611.A8D332BC11@toro.w3.mag.keio.ac.jp>
Mention that tasks from discarded documents are also discarded. Change
some prose to mention origins and sites instead of domains. Fire
'storage' on inactive documents as well so they all get notified.
(whatwg r3026)

6 Privacy
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#privacy
setItem(key, value)
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#dom-storage-setitem
3.5 The storage event
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#the-storage-event
5 Disk space
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#disk-space
removeItem(key)
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#dom-storage-removeitem
4.2 Databases
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#databases
7
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#dom-sqlerror-code-7
4.1 Introduction
http://people.w3.org/mike/diffs/html5/webstorage/Overview.1.35.html#introduction-0

http://people.w3.org/mike/diffs/html5/webstorage/Overview.diff.html
http://dev.w3.org/cvsweb/html5/webstorage/Overview.html?r1=1.34&r2=1.35&f=h
http://html5.org/tools/web-apps-tracker?from=3025&to=3026

===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- Overview.html	29 Apr 2009 08:02:49 -0000	1.34
+++ Overview.html	29 Apr 2009 08:29:34 -0000	1.35
@@ -442,7 +442,7 @@
   list, then it must have its value updated to the value given in the
   <var title="">value</var> argument.<p>If it couldn't set the new value, the method must raise an
   <code>QUOTA_EXCEEDED_ERR</code> exception. (Setting could fail if,
-  e.g., the user has disabled storage for the domain, or if the quota
+  e.g., the user has disabled storage for the site, or if the quota
   has been exceeded.)<p>The <dfn id="dom-storage-removeitem" title="dom-Storage-removeItem"><code>removeItem(<var title="">key</var>)</code></dfn> method must cause the key/value
   pair with the given <var title="">key</var> to be removed from the
   list associated with the object, if it exists. If no item with that
@@ -538,9 +538,11 @@
   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
+  <code>Window</code> object whose <code>Document</code> object has a
+  <code><a href="#storage-0">Storage</a></code> object that is affected.<p class="note">This includes <code>Document</code> objects that are
+  not <span>fully active</span>, but events fired on those are ignored
+  by the <span>event loop</span> until the <code>Document</code>
+  becomes <span>fully active</span> again.<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>
@@ -602,7 +604,7 @@
    executeSql('SELECT rowid FROM t WHERE c IN (' + q + ')', array, ...);
 --><h3 id="databases"><span class="secno">4.2 </span>Databases</h3><p>Each <i>origin</i> has an associated set of databases. Each
   database has a name and a current version. There is no way to
-  enumerate or delete the databases available for a domain from this
+  enumerate or delete the databases available for an origin from this
   API.<p class="note">Each database has one version at a time; a database
   can't exist in multiple versions at once. Versions are intended to
   allow authors to manage schema changes incrementally and
@@ -1161,17 +1163,17 @@
 
   </table><h2 id="disk-space"><span class="secno">5 </span>Disk space</h2><p>User agents should limit the total amount of space allowed for
   storage areas and databases.<p>User agents should guard against sites storing data in the
-  storage areas or databases of subdomains, e.g. storing up to the
-  limit in a1.example.com, a2.example.com, a3.example.com, etc,
-  circumventing the main example.com storage limit.<p>User agents may prompt the user when quotas are reached, allowing
+  storage areas or databases of other affiliated sites, e.g. storing
+  up to the limit in a1.example.com, a2.example.com, a3.example.com,
+  etc, circumventing the main example.com storage limit.<p>User agents may prompt the user when quotas are reached, allowing
   the user to grant a site more space. This enables sites to store
   many user-created documents on the user's computer, for
   instance.<p>User agents should allow users to see how much space each domain
   is using.</p><!--<p>If the storage area space limit is reached during a <code
   title="dom-Storage-setItem">setItem()</code> call, the method will
-  raise an exception.</p>--><p>A mostly arbitrary limit of five megabytes per domain is
-  recommended. Implementation feedback is welcome and will be used to
-  update this suggestion in future.<h2 id="privacy"><span class="secno">6 </span>Privacy</h2><h3 id="user-tracking"><span class="secno">6.1 </span>User tracking</h3><p>A third-party advertiser (or any entity capable of getting
+  raise an exception.</p>--><p>A mostly arbitrary limit of five megabytes per
+  <span>origin</span> is recommended. Implementation feedback is
+  welcome and will be used to update this suggestion in future.<h2 id="privacy"><span class="secno">6 </span>Privacy</h2><h3 id="user-tracking"><span class="secno">6.1 </span>User tracking</h3><p>A third-party advertiser (or any entity capable of getting
   content distributed to multiple sites) could use a unique identifier
   stored in its local storage area or in its client-side database to
   track a user across multiple sessions, building a profile of the
Received on Wednesday, 29 April 2009 08:36:48 GMT

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