[html5] r7674 - [e] (0) Clarify a note Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=197 [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2013-01-30 15:20:29 -0800 (Wed, 30 Jan 2013)
New Revision: 7674

Modified:
   complete.html
   index
   source
Log:
[e] (0) Clarify a note
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=19706
Affected topics: Offline Web Applications

Modified: complete.html
===================================================================
--- complete.html	2013-01-30 23:02:17 UTC (rev 7673)
+++ complete.html	2013-01-30 23:20:29 UTC (rev 7674)
@@ -71059,13 +71059,13 @@
   progress</dfn>. Support for this is optional. Caching progress UI could consist of a progress bar
   or message panel in the user agent's interface, or an overlay, or something else. Certain events
   fired during the <a href=#application-cache-download-process>application cache download process</a> allow the script to override the
-  display of such an interface. The goal of this is to allow Web applications to provide more
+  display of such an interface. (Such events are delayed until after the <code title=event-load>load</code> event has fired.)
+
+  The goal of this is to allow Web applications to provide more
   seamless update mechanisms, hiding from the user the mechanics of the application cache mechanism.
   User agents may display user interfaces independent of this, but are encouraged to not show
   prominent update progress notifications for applications that cancel the relevant events.</p>
 
-  <p class=note>These events are delayed until after the <code title=event-load>load</code> event has fired.</p>
-
   <p>The <a href=#application-cache-download-process>application cache download process</a> steps are as follows:
 
   <ol><li><p>Optionally, wait until the permission to start the <a href=#application-cache-download-process>application cache download

Modified: index
===================================================================
--- index	2013-01-30 23:02:17 UTC (rev 7673)
+++ index	2013-01-30 23:20:29 UTC (rev 7674)
@@ -71059,13 +71059,13 @@
   progress</dfn>. Support for this is optional. Caching progress UI could consist of a progress bar
   or message panel in the user agent's interface, or an overlay, or something else. Certain events
   fired during the <a href=#application-cache-download-process>application cache download process</a> allow the script to override the
-  display of such an interface. The goal of this is to allow Web applications to provide more
+  display of such an interface. (Such events are delayed until after the <code title=event-load>load</code> event has fired.)
+
+  The goal of this is to allow Web applications to provide more
   seamless update mechanisms, hiding from the user the mechanics of the application cache mechanism.
   User agents may display user interfaces independent of this, but are encouraged to not show
   prominent update progress notifications for applications that cancel the relevant events.</p>
 
-  <p class=note>These events are delayed until after the <code title=event-load>load</code> event has fired.</p>
-
   <p>The <a href=#application-cache-download-process>application cache download process</a> steps are as follows:
 
   <ol><li><p>Optionally, wait until the permission to start the <a href=#application-cache-download-process>application cache download

Modified: source
===================================================================
--- source	2013-01-30 23:02:17 UTC (rev 7673)
+++ source	2013-01-30 23:20:29 UTC (rev 7674)
@@ -83130,14 +83130,14 @@
   progress</dfn>. Support for this is optional. Caching progress UI could consist of a progress bar
   or message panel in the user agent's interface, or an overlay, or something else. Certain events
   fired during the <span>application cache download process</span> allow the script to override the
-  display of such an interface. The goal of this is to allow Web applications to provide more
+  display of such an interface. (Such events are delayed until after the <code
+  title="event-load">load</code> event has fired.)
+
+  The goal of this is to allow Web applications to provide more
   seamless update mechanisms, hiding from the user the mechanics of the application cache mechanism.
   User agents may display user interfaces independent of this, but are encouraged to not show
   prominent update progress notifications for applications that cancel the relevant events.</p>
 
-  <p class="note">These events are delayed until after the <code
-  title="event-load">load</code> event has fired.</p>
-
   <p>The <span>application cache download process</span> steps are as follows:
 
   <ol>