Skip to content

Commit

Permalink
[e] (0) Clarify a note
Browse files Browse the repository at this point in the history
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=19706
Affected topics: Offline Web Applications

git-svn-id: http://svn.whatwg.org/webapps@7674 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 30, 2013
1 parent c0c2724 commit d39ba79
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 10 deletions.
6 changes: 3 additions & 3 deletions complete.html
Expand Up @@ -71059,13 +71059,13 @@ <h4 id=downloading-or-updating-an-application-cache><span class=secno>6.7.4 </sp
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
Expand Down
6 changes: 3 additions & 3 deletions index
Expand Up @@ -71059,13 +71059,13 @@ NETWORK:
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
Expand Down
8 changes: 4 additions & 4 deletions source
Expand Up @@ -83130,14 +83130,14 @@ NETWORK:
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>
Expand Down

0 comments on commit d39ba79

Please sign in to comment.