[e] (0) Clarify the issue regarding appcaches and cookie UI.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7785 git-svn-id: http://svn.whatwg.org/webapps@4173 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 18, 2009 · c05ba52 · c05ba52
1 parent 174981d
commit c05ba52
Show file tree

Hide file tree

Showing 3 changed files with 36 additions and 21 deletions.
diff --git a/complete.html b/complete.html
@@ -54200,13 +54200,18 @@ <h4 id=expiring-application-caches><span class=secno>6.9.7 </span>Expiring appli
   caches, except on request from the user, or after having been left
   unused for an extended period of time.</p>
 
-  <p>Implementors are encouraged to expose application caches in a
-  manner related to HTTP cookies, allowing caches to be expired
-  together with cookies and other origin-specific data. Application
-  caches and cookies have similar implications with respect to privacy
-  (e.g. if the site can identify the user when providing the cache, it
-  can store data in the cache that can be used for cookie
-  resurrection).</p>
+  <p>Application caches and cookies have similar implications with
+  respect to privacy (e.g. if the site can identify the user when
+  providing the cache, it can store data in the cache that can be used
+  for cookie resurrection). Implementors are therefore encouraged to
+  expose application caches in a manner related to HTTP cookies,
+  allowing caches to be expunged together with cookies and other
+  origin-specific data.</p>
+
+  <p class=example>For example, a user agent could have a "delete
+  site-specific data" feature that clears all cookies, application
+  caches, local storage, databases, etc, from an origin all at
+  once.</p>
 
 
 

diff --git a/index b/index
@@ -51359,13 +51359,18 @@ NETWORK:
   caches, except on request from the user, or after having been left
   unused for an extended period of time.</p>
 
-  <p>Implementors are encouraged to expose application caches in a
-  manner related to HTTP cookies, allowing caches to be expired
-  together with cookies and other origin-specific data. Application
-  caches and cookies have similar implications with respect to privacy
-  (e.g. if the site can identify the user when providing the cache, it
-  can store data in the cache that can be used for cookie
-  resurrection).</p>
+  <p>Application caches and cookies have similar implications with
+  respect to privacy (e.g. if the site can identify the user when
+  providing the cache, it can store data in the cache that can be used
+  for cookie resurrection). Implementors are therefore encouraged to
+  expose application caches in a manner related to HTTP cookies,
+  allowing caches to be expunged together with cookies and other
+  origin-specific data.</p>
+
+  <p class=example>For example, a user agent could have a "delete
+  site-specific data" feature that clears all cookies, application
+  caches, local storage, databases, etc, from an origin all at
+  once.</p>
 
 
 

diff --git a/source b/source
@@ -61118,13 +61118,18 @@ NETWORK:
   caches, except on request from the user, or after having been left
   unused for an extended period of time.</p>
 
-  <p>Implementors are encouraged to expose application caches in a
-  manner related to HTTP cookies, allowing caches to be expired
-  together with cookies and other origin-specific data. Application
-  caches and cookies have similar implications with respect to privacy
-  (e.g. if the site can identify the user when providing the cache, it
-  can store data in the cache that can be used for cookie
-  resurrection).</p>
+  <p>Application caches and cookies have similar implications with
+  respect to privacy (e.g. if the site can identify the user when
+  providing the cache, it can store data in the cache that can be used
+  for cookie resurrection). Implementors are therefore encouraged to
+  expose application caches in a manner related to HTTP cookies,
+  allowing caches to be expunged together with cookies and other
+  origin-specific data.</p>
+
+  <p class="example">For example, a user agent could have a "delete
+  site-specific data" feature that clears all cookies, application
+  caches, local storage, databases, etc, from an origin all at
+  once.</p>