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

hixie: Clarify the issue regarding appcaches and cookie UI. (whatwg r4173)

From: poot <cvsmail@w3.org>
Date: Mon, 19 Oct 2009 08:46:57 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20091018234657.638792BC06@toro.w3.mag.keio.ac.jp>
hixie: Clarify the issue regarding appcaches and cookie UI. (whatwg
r4173)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3319&r2=1.3320&f=h
http://html5.org/tools/web-apps-tracker?from=4172&to=4173

===================================================================
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:47:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:09:01 UTC