W3C home > Mailing lists > Public > public-html-commits@w3.org > January 2011

html5/spec Overview.html,1.4620,1.4621

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 11 Jan 2011 00:03:52 +0000
To: public-html-commits@w3.org
Message-Id: <E1PcRiK-0003US-9t@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv13387

Modified Files:
	Overview.html 
Log Message:
Suggest that UAs can allow users to trust sites to have more quota. (whatwg r5760)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4620
retrieving revision 1.4621
diff -u -d -r1.4620 -r1.4621
--- Overview.html	10 Jan 2011 23:17:04 -0000	1.4620
+++ Overview.html	11 Jan 2011 00:03:48 -0000	1.4621
@@ -47083,23 +47083,49 @@
   primed the first time), making the testing of offline applications
   simpler.</p>
 
-  </div><h4 id="expiring-application-caches"><span class="secno">5.6.7 </span>Expiring application caches</h4><p>As a general rule, user agents should not expire application
+  </div><div class="impl">
+
+  <h4 id="expiring-application-caches"><span class="secno">5.6.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>Application caches and cookies have similar implications with
+  unused for an extended period of time.</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 class="example">For example, a user agent could have a "delete
+  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.<h4 id="disk-space"><span class="secno">5.6.8 </span>Disk space</h4><p>User agents should consider applying constraints on disk usage of
+  once.</p>
+
+  </div><div class="impl">
+
+  <h4 id="disk-space"><span class="secno">5.6.8 </span>Disk space</h4>
+
+  <p>User agents should consider applying constraints on disk usage of
   <a href="#application-cache" title="application cache">application caches</a>, and care
   should be taken to ensure that the restrictions cannot be easily
-  worked around using subdomains.<p>User agents should allow users to see how much space each domain
+  worked around using subdomains.</p>
+
+  <p>User agents should allow users to see how much space each domain
   is using, and may offer the user the ability to delete specific
-  <a href="#application-cache" title="application cache">application caches</a>.<h4 id="application-cache-api"><span class="secno">5.6.9 </span>Application cache API</h4><pre class="idl">interface <dfn id="applicationcache">ApplicationCache</dfn> {
+  <a href="#application-cache" title="application cache">application caches</a>.</p>
+
+  <p class="note">How quotas are presented to the user is not defined
+  by this specification. User agents are encouraged to provide
+  features such as allowing a user to indicate that certain sites are
+  trusted to use more than the default quota, e.g. by asynchronously
+  presenting a user interface while a cache is being updated, or by
+  having an explicit whitelist in the user agent's configuration
+  interface.</p>
+
+  </div><h4 id="application-cache-api"><span class="secno">5.6.9 </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 Tuesday, 11 January 2011 00:03:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:03:56 GMT