W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2009

html5/spec Overview.html,1.3319,1.3320

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 18 Oct 2009 23:46:49 +0000
To: public-html-commits@w3.org
Message-Id: <E1MzfSb-0003Xu-Db@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv13616

Modified Files:
	Overview.html 
Log Message:
Clarify the issue regarding appcaches and cookie UI. (whatwg r4173)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3319
retrieving revision 1.3320
diff -u -d -r1.3319 -r1.3320
--- Overview.html	18 Oct 2009 23:40:06 -0000	1.3319
+++ Overview.html	18 Oct 2009 23:46:46 -0000	1.3320
@@ -46124,13 +46124,16 @@
 
   </div><h4 id="expiring-application-caches"><span class="secno">6.9.7 </span>Expiring application caches</h4><p>As a general rule, user agents should not expire application
   caches, except on request from the user, or after having been left
-  unused for an extended period of time.<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).<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> {
+  unused for an extended period of time.<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 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.<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> {
 
   // <a href="#concept-appcache-status" title="concept-appcache-status">update status</a>
   const unsigned short <a href="#dom-appcache-uncached" title="dom-appcache-UNCACHED">UNCACHED</a> = 0;
Received on Sunday, 18 October 2009 23:46:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 18 October 2009 23:46:51 GMT