- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 13 Oct 2009 01:51:31 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/webstorage
In directory hutz:/tmp/cvs-serv15955
Modified Files:
Overview.html
Log Message:
Remove a contradiction (can you delete data or not?) (whatwg r4120)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/webstorage/Overview.html,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -d -r1.84 -r1.85
--- Overview.html 13 Oct 2009 01:34:50 -0000 1.84
+++ Overview.html 13 Oct 2009 01:51:29 -0000 1.85
@@ -650,14 +650,14 @@
<dt>Expiring stored data</dt>
<dd>
- <p>User agents may automatically delete stored data after a period
- of time.</p>
+ <p>User agents may, if so configured by the user, automatically
+ delete stored data after a period of time.</p>
- <p>For example, a user agent could treat third-party local
- storage areas as session-only storage, deleting the data once the
- user had closed all the <span>browsing contexts</span> that could
- access it.</p>
+ <p>For example, a user agent could be configured to treat
+ third-party local storage areas as session-only storage, deleting
+ the data once the user had closed all the <span>browsing
+ contexts</span> that could access it.</p>
<p>This can restrict the ability of a site to track a user, as the
@@ -665,7 +665,10 @@
sessions when he authenticates with the site itself (e.g. by
making a purchase or logging in to a service).</p>
- <p>However, this also puts the user's data at risk.</p>
+ <p>However, this also reduces the usefulness of the API as a
+ long-term storage mechanism. It can also put the user's data at
+ risk, if the user does not fully understand the implications of
+ data expiration.</p>
<!--v2 consider adding an explicit way for sites to state when
Received on Tuesday, 13 October 2009 01:51:36 UTC