[html5] r4213 - [giow] (0) Allow UAs to avoid starting the caching algorithm until the network i [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-20 15:08:15 -0700 (Tue, 20 Oct 2009)
New Revision: 4213

Modified:
   complete.html
   index
   source
Log:
[giow] (0) Allow UAs to avoid starting the caching algorithm until the network is up.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7859

Modified: complete.html
===================================================================
--- complete.html	2009-10-20 22:06:06 UTC (rev 4212)
+++ complete.html	2009-10-20 22:08:15 UTC (rev 4213)
@@ -53528,12 +53528,13 @@
 
   <ol><li><p>Optionally, wait until the permission to start the
    <a href=#application-cache-download-process>application cache download process</a> has been obtained
-   from the user. This could include doing nothing until the user
-   explicitly opts-in to caching the site, or could involve prompting
-   the user for permission. The algorithm might never get past this
-   point. (This step is particularly intended to be used by user
-   agents running on severely space-constrained devices or in highly
-   privacy-sensitive environments).</li>
+   from the user and until the user agent is confident that the
+   network is available. This could include doing nothing until the
+   user explicitly opts-in to caching the site, or could involve
+   prompting the user for permission. The algorithm might never get
+   past this point. (This step is particularly intended to be used by
+   user agents running on severely space-constrained devices or in
+   highly privacy-sensitive environments).</li>
 
    <li>
 

Modified: index
===================================================================
--- index	2009-10-20 22:06:06 UTC (rev 4212)
+++ index	2009-10-20 22:08:15 UTC (rev 4213)
@@ -50687,12 +50687,13 @@
 
   <ol><li><p>Optionally, wait until the permission to start the
    <a href=#application-cache-download-process>application cache download process</a> has been obtained
-   from the user. This could include doing nothing until the user
-   explicitly opts-in to caching the site, or could involve prompting
-   the user for permission. The algorithm might never get past this
-   point. (This step is particularly intended to be used by user
-   agents running on severely space-constrained devices or in highly
-   privacy-sensitive environments).</li>
+   from the user and until the user agent is confident that the
+   network is available. This could include doing nothing until the
+   user explicitly opts-in to caching the site, or could involve
+   prompting the user for permission. The algorithm might never get
+   past this point. (This step is particularly intended to be used by
+   user agents running on severely space-constrained devices or in
+   highly privacy-sensitive environments).</li>
 
    <li>
 

Modified: source
===================================================================
--- source	2009-10-20 22:06:06 UTC (rev 4212)
+++ source	2009-10-20 22:08:15 UTC (rev 4213)
@@ -60269,12 +60269,13 @@
 
    <li><p>Optionally, wait until the permission to start the
    <span>application cache download process</span> has been obtained
-   from the user. This could include doing nothing until the user
-   explicitly opts-in to caching the site, or could involve prompting
-   the user for permission. The algorithm might never get past this
-   point. (This step is particularly intended to be used by user
-   agents running on severely space-constrained devices or in highly
-   privacy-sensitive environments).</p></li>
+   from the user and until the user agent is confident that the
+   network is available. This could include doing nothing until the
+   user explicitly opts-in to caching the site, or could involve
+   prompting the user for permission. The algorithm might never get
+   past this point. (This step is particularly intended to be used by
+   user agents running on severely space-constrained devices or in
+   highly privacy-sensitive environments).</p></li>
 
    <li>