[html5] r4120 - [e] (0) Remove a contradiction (can you delete data or not?)

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-12 19:02:38 -0700 (Mon, 12 Oct 2009)
New Revision: 4120

Modified:
   complete.html
   source
Log:
[e] (0) Remove a contradiction (can you delete data or not?)

Modified: complete.html
===================================================================
--- complete.html	2009-10-13 01:45:58 UTC (rev 4119)
+++ complete.html	2009-10-13 02:02:38 UTC (rev 4120)
@@ -57441,14 +57441,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
@@ -57456,7 +57456,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

Modified: source
===================================================================
--- source	2009-10-13 01:45:58 UTC (rev 4119)
+++ source	2009-10-13 02:02:38 UTC (rev 4120)
@@ -64940,14 +64940,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>
 
     <!--END database-->
-    <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>
     <!--START database-->
 
     <p>This can restrict the ability of a site to track a user, as the
@@ -64955,7 +64955,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>
 
     <!--END database-->
     <!--v2 consider adding an explicit way for sites to state when