[html5] r4173 - [e] (0) Clarify the issue regarding appcaches and cookie UI. Fixing http://www.w [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-18 16:59:01 -0700 (Sun, 18 Oct 2009)
New Revision: 4173

Modified:
   complete.html
   index
   source
Log:
[e] (0) Clarify the issue regarding appcaches and cookie UI.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7785

Modified: complete.html
===================================================================
--- complete.html	2009-10-18 23:52:22 UTC (rev 4172)
+++ complete.html	2009-10-18 23:59:01 UTC (rev 4173)
@@ -54200,16 +54200,21 @@
   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>
 
 
+
   <h4 id=application-cache-api><span class=secno>6.9.8 </span>Application cache API</h4>
 
   <pre class=idl>interface <dfn id=applicationcache>ApplicationCache</dfn> {

Modified: index
===================================================================
--- index	2009-10-18 23:52:22 UTC (rev 4172)
+++ index	2009-10-18 23:59:01 UTC (rev 4173)
@@ -51359,16 +51359,21 @@
   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>
 
 
+
   <h4 id=application-cache-api><span class=secno>6.9.8 </span>Application cache API</h4>
 
   <pre class=idl>interface <dfn id=applicationcache>ApplicationCache</dfn> {

Modified: source
===================================================================
--- source	2009-10-18 23:52:22 UTC (rev 4172)
+++ source	2009-10-18 23:59:01 UTC (rev 4173)
@@ -61118,16 +61118,21 @@
   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>
 
 
+
   <h4>Application cache API</h4>
 
   <pre class="idl">interface <dfn>ApplicationCache</dfn> {