[html5] r2919 - [e] (0) Rephrase the appcache section to talk about 'cache hosts' instead of doc [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Mar 27 17:35:09 PDT 2009
Author: ianh
Date: 2009-03-27 17:35:07 -0700 (Fri, 27 Mar 2009)
New Revision: 2919
Modified:
index
source
Log:
[e] (0) Rephrase the appcache section to talk about 'cache hosts' instead of documents and browsing contexts.
Modified: index
===================================================================
--- index 2009-03-27 00:48:17 UTC (rev 2918)
+++ index 2009-03-28 00:35:07 UTC (rev 2919)
@@ -39,7 +39,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
- <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 27 March 2009</h2>
+ <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 28 March 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<dl><dt>Multiple-page version:</dt>
@@ -42132,11 +42132,22 @@
must be ignored when looking at what <a href=#application-cache-group title="application cache
group">application cache groups</a> exist.</p>
- <hr><p>A <code>Document</code> initially is not associated with an
- <a href=#application-cache>application cache</a>, but steps <a href=#parser-appcache>in the parser</a> and in the <a href=#navigate title=navigate>navigation</a> sections cause <a href=#concept-appcache-init title=concept-appcache-init>cache selection</a> to occur early
- in the page load process.</p>
+ <hr><p>A <dfn id=cache-host>cache host</dfn> is a <code>Document</code> or a
+ <code>SharedWorkerGlobalScope</code> object. A <a href=#cache-host>cache
+ host</a> can be associated with an <a href=#application-cache>application
+ cache</a>.</p>
- <p>Multiple <a href=#application-cache title="application cache">application
+ <p>A <code>Document</code> initially is not associated with an
+ <a href=#application-cache>application cache</a>, buu can become associated with one
+ early during the page load process, when steps <a href=#parser-appcache>in the parser</a> and in the <a href=#navigate title=navigate>navigation</a> sections that cause <a href=#concept-appcache-init title=concept-appcache-init>cache selection</a> to occur.</p>
+
+ <p>A <code>SharedWorkerGlobalScope</code> is can be associated with
+ an <a href=#application-cache>application cache</a> when it is created.</p>
+
+ <p>Each <a href=#cache-host>cache host</a> has an associated
+ <code><a href=#applicationcache>ApplicationCache</a></code> object.</p>
+
+ <hr><p>Multiple <a href=#application-cache title="application cache">application
caches</a> in different <a href=#application-cache-group title="application cache
group">application cache groups</a> can contain the same
resource, e.g. if the manifests all reference that resource. If the
@@ -42564,7 +42575,7 @@
process</dfn> for an <a href=#absolute-url>absolute URL</a> purported to identify
a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>, or for an
<a href=#application-cache-group>application cache group</a>, potentially given a particular
- <a href=#browsing-context>browsing context</a>, and potentially given a new <a href=#concept-appcache-master title=concept-appcache-master>master</a> resource, the user
+ <a href=#cache-host>cache host</a>, and potentially given a new <a href=#concept-appcache-master title=concept-appcache-master>master</a> resource, the user
agent must run the following steps:</p>
<ol><li>
@@ -42614,19 +42625,19 @@
<var title="">cache group</var>'s <a href=#concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
entries</a>.</li>
- <li><p>If these steps were invoked with a <a href=#browsing-context>browsing
- context</a>, and the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> is <i>checking</i> or
+ <li><p>If these steps were invoked with a <a href=#cache-host>cache
+ host</a>, and the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> is <i>checking</i> or
<i>downloading</i>, then <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
a simple event</a> called <code title=event-checking>checking</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#browsing-context>browsing
- context</a>.</li>
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#cache-host>cache
+ host</a>.</li>
- <li><p>If these steps were invoked with a <a href=#browsing-context>browsing
- context</a>, and the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> is <i>downloading</i>, then also
+ <li><p>If these steps were invoked with a <a href=#cache-host>cache
+ host</a>, and the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> is <i>downloading</i>, then also
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
called <code title=event-downloading>downloading</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#browsing-context>browsing
- context</a>.</li>
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#cache-host>cache
+ host</a>.</li>
<li><p>If the <a href=#concept-appcache-status title=concept-appcache-status>status</a>
of the <var title="">cache group</var> is either <i>checking</i>
@@ -42635,12 +42646,12 @@
<li><p>Set the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> to <i>checking</i>.</p>
- <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application
- cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-checking>checking</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an
+ <a href=#application-cache>application cache</a> in <var title="">cache
+ group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-checking>checking</code>
+ at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
display of some sort of user interface indicating to the user
that the user agent is checking for the availability of
updates.</li>
@@ -42655,11 +42666,11 @@
</li>
<li><p>If this is a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
- attempt</a>, then this algorithm was invoked with a
- <a href=#browsing-context>browsing context</a>; <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-checking>checking</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#browsing-context>browsing
- context</a>.</li>
+ attempt</a>, then this algorithm was invoked with a <a href=#cache-host>cache
+ host</a>; <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-checking>checking</code> at
+ the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#cache-host>cache
+ host</a>.</li>
<li>
@@ -42686,12 +42697,12 @@
than the processing of <code>Document</code> objects already
associated with an <a href=#application-cache>application cache</a> in the <var title="">cache group</var>.</li>
- <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application
- cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-obsolete>obsolete</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an
+ <a href=#application-cache>application cache</a> in <var title="">cache
+ group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-obsolete>obsolete</code>
+ at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
display of some sort of user interface indicating to the user
that the application is no longer available for offline
use.</li>
@@ -42700,12 +42711,12 @@
entries</a>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
event</a> called <code title=event-error><a href=#event-error>error</a></code> (not
<code title=event-obsolete>obsolete</code>!) at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a> whose <a href=#active-document>active document</a> is the
- <code>Document</code> for this entry, if there still is one. The
- default action of this event should be the display of some sort
- of user interface indicating to the user that the user agent
- failed to save the application for offline use.</li>
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a> the <code>Document</code> for this entry, if there
+ still is one. The default action of this event should be the
+ display of some sort of user interface indicating to the user
+ that the user agent failed to save the application for offline
+ use.</li>
<li><p>If <var title="">cache group</var> has an
<a href=#application-cache>application cache</a> whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness flag</a> is
@@ -42755,12 +42766,12 @@
<p>If the download failed (e.g. the connection times out, or the
user cancels the download), then <a href=#queue-a-task>queue a task</a> to
<a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-error><a href=#event-error>error</a></code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a> whose <a href=#active-document>active document</a> is the
- <code>Document</code> for this entry, if there still is one. The
- default action of this event should be the display of some sort
- of user interface indicating to the user that the user agent
- failed to save the application for offline use.</p>
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a> the <code>Document</code> for this entry, if there
+ still is one. The default action of this event should be the
+ display of some sort of user interface indicating to the user
+ that the user agent failed to save the application for offline
+ use.</p>
<p>Otherwise, associate the <code>Document</code> for this entry
with <var title="">cache</var>; store the resource for this
@@ -42773,12 +42784,12 @@
</li>
- <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application
- cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-noupdate>noupdate</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an
+ <a href=#application-cache>application cache</a> in <var title="">cache
+ group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-noupdate>noupdate</code>
+ at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
display of some sort of user interface indicating to the user
that the application is up to date.</li>
@@ -42806,12 +42817,12 @@
<li><p>Set the <a href=#concept-appcache-status title=concept-appcache-status>status</a>
of <var title="">cache group</var> to <i>downloading</i>.</li>
- <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application
- cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-downloading>downloading</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an
+ <a href=#application-cache>application cache</a> in <var title="">cache group</var>,
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
+ called <code title=event-downloading>downloading</code> at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
display of some sort of user interface indicating to the user that
a new version is being downloaded.</li>
@@ -42856,12 +42867,12 @@
</li>
- <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application
- cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-progress><a href=#event-progress>progress</a></code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
+ <li><p>For each <a href=#cache-host>cache host</a> associated with an
+ <a href=#application-cache>application cache</a> in <var title="">cache
+ group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-progress><a href=#event-progress>progress</a></code>
+ at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
display of some sort of user interface indicating to the user
that a file is being downloaded in preparation for updating the
application.</li> <!-- XXX need to include progress
@@ -42994,10 +43005,9 @@
<ol><li><p>Unassociate the <code>Document</code> for this entry from
<var title="">new cache</var>.</li>
- <li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-error><a href=#event-error>error</a></code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a> whose <a href=#active-document>active document</a> is the
+ <li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
+ event</a> called <code title=event-error><a href=#event-error>error</a></code> at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the
<code>Document</code> for this entry, if there still is one. The
default action of this event should be the display of some sort
of user interface indicating to the user that the user agent
@@ -43061,26 +43071,24 @@
<li>
<p>If this is a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
- attempt</a>, then for each <a href=#browsing-context>browsing context</a>
- whose <a href=#active-document>active document</a> is associated with an
- <a href=#application-cache>application cache</a> in <var title="">cache
+ attempt</a>, then for each <a href=#cache-host>cache host</a> associated
+ with an <a href=#application-cache>application cache</a> in <var title="">cache
group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
event</a> called <code title=event-cached>cached</code> at
- the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the
- <a href=#browsing-context>browsing context</a>. The default action of these
- events should be the display of some sort of user interface
- indicating to the user that the application has been cached and
- that they can now use it offline.</p>
+ the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
+ display of some sort of user interface indicating to the user that
+ the application has been cached and that they can now use it
+ offline.</p>
- <p>Otherwise, it is an <a href=#concept-appcache-upgrade title=concept-appcache-upgrade>upgrade attempt</a>. For
- each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application
+ <p>Otherwise, it is an <a href=#concept-appcache-upgrade title=concept-appcache-upgrade>upgrade attempt</a>. For each
+ <a href=#cache-host>cache host</a> associated with an <a href=#application-cache>application
cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-updateready>updateready</code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
- display of some sort of user interface indicating to the user
- that a new version is available and that they can activate it by
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
+ display of some sort of user interface indicating to the user that
+ a new version is available and that they can activate it by
reloading the page.</p>
</li>
@@ -43108,8 +43116,7 @@
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
event</a> called <code title=event-error><a href=#event-error>error</a></code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a> whose <a href=#active-document>active document</a> is the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the
<code>Document</code> for this entry, if there still is one. The
default action of these events should be the display of some sort
of user interface indicating to the user that the user agent
@@ -43117,12 +43124,12 @@
</ol></li>
- <li><p>For each <a href=#browsing-context>browsing context</a> whose <a href=#active-document>active
- document</a> is still associated with an <a href=#application-cache>application
- cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-error><a href=#event-error>error</a></code> at the
- <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#browsing-context>browsing
- context</a>. The default action of these events should be the
+ <li><p>For each <a href=#cache-host>cache host</a> still associated with an
+ <a href=#application-cache>application cache</a> in <var title="">cache group</var>,
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
+ called <code title=event-error><a href=#event-error>error</a></code> at the
+ <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
+ host</a>. The default action of these events should be the
display of some sort of user interface indicating to the user that
the user agent failed to save the application for offline
use.</li>
@@ -43138,7 +43145,8 @@
<li><p>If appropriate, remove any user interface indicating that an
update for this cache is in progress.</li>
- <li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> be <i>idle</i>.</li>
+ <li><p>Let the <a href=#concept-appcache-status title=concept-appcache-status>status</a>
+ of <var title="">cache group</var> be <i>idle</i>.</li>
<li><p>If this was a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
attempt</a>, discard <var title="">cache group</var>
@@ -43153,9 +43161,9 @@
<hr><p>User agents may invoke the <a href=#application-cache-update-process>application cache update
process</a>, in the background, for any <a href=#application-cache>application
- cache</a>, at any time (with no <a href=#browsing-context>browsing
- context</a>). This allows user agents to keep caches primed and
- to update caches even before the user visits a site.</p>
+ cache</a>, at any time (with no <a href=#cache-host>cache host</a>). This
+ allows user agents to keep caches primed and to update caches even
+ before the user visits a site.</p>
@@ -43273,13 +43281,13 @@
</dl><h5 id=changesToNetworkingModel><span class=secno>5.8.6.1 </span>Changes to the networking model</h5>
- <p>When a <a href=#browsing-context>browsing context</a>'s <a href=#active-document>active
- document</a> is associated with an <a href=#application-cache>application cache</a>
- whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness
- flag</a> is <i>complete</i>, any and all loads for resources in
- that <a href=#browsing-context>browsing context</a> other than those for <a href=#child-browsing-context title="child browsing context">child browsing contexts</a> must
- go through the following steps instead of immediately invoking the
- mechanisms appropriate to that resource's scheme:</p>
+ <p>When a <a href=#cache-host>cache host</a> is associated with an
+ <a href=#application-cache>application cache</a> whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness flag</a> is
+ <i>complete</i>, any and all loads for resources related to that
+ <a href=#cache-host>cache host</a> other than those for <a href=#child-browsing-context title="child
+ browsing context">child browsing contexts</a> must go through the
+ following steps instead of immediately invoking the mechanisms
+ appropriate to that resource's scheme:</p>
<ol><li><p>If the resource is not to be fetched using the HTTP GET
mechanism <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or
@@ -43359,14 +43367,28 @@
};</pre>
- <dl class=domintro><dt><var title="">window</var> . <code title=dom-applicationCache><a href=#dom-applicationcache>applicationCache</a></code> . <code title=dom-appcache-status><a href=#dom-appcache-status>status</a></code></dt>
+ <dl class=domintro><dt><var title="">cache</var> = <var title="">window</var> . <code title=dom-applicationCache><a href=#dom-applicationcache>applicationCache</a></code></dt>
<dd>
+ <p>(In a window.) Returns the <code><a href=#applicationcache>ApplicationCache</a></code> object that applies to the <a href=#active-document>active document</a> of that <code><a href=#window>Window</a></code>.</p>
+
+ </dd>
+
+ <dt><var title="">cache</var> = <var title="">self</var> . <code title=dom-applicationCache><a href=#dom-applicationcache>applicationCache</a></code></dt>
+ <dd>
+
+ <p>(In a shared worker.) Returns the <code><a href=#applicationcache>ApplicationCache</a></code> object that applies to the current shared worker.</p>
+
+ </dd>
+
+ <dt><var title="">cache</var> . <code title=dom-appcache-status><a href=#dom-appcache-status>status</a></code></dt>
+ <dd>
+
<p>Returns the current status of the application cache, as given by the constants defined below.</p>
</dd>
- <dt><var title="">window</var> . <code title=dom-applicationCache><a href=#dom-applicationcache>applicationCache</a></code> . <code title=dom-appcache-update><a href=#dom-appcache-update>update</a></code>()</dt>
+ <dt><var title="">cache</var> . <code title=dom-appcache-update><a href=#dom-appcache-update>update</a></code>()</dt>
<dd>
<p>Invokes the application cache update process.</p>
@@ -43375,7 +43397,7 @@
</dd>
- <dt><var title="">window</var> . <code title=dom-applicationCache><a href=#dom-applicationcache>applicationCache</a></code> . <code title=dom-appcache-swapCache><a href=#dom-appcache-swapcache>swapCache</a></code>()</dt>
+ <dt><var title="">cache</var> . <code title=dom-appcache-swapCache><a href=#dom-appcache-swapcache>swapCache</a></code>()</dt>
<dd>
<p>Switches to the most recent application cache, if there is a newer one. If there isn't, throws an <code><a href=#invalid_access_err>INVALID_ACCESS_ERR</a></code> exception.</p>
@@ -43387,110 +43409,105 @@
<p>Objects implementing the <code><a href=#applicationcache>ApplicationCache</a></code> interface
must also implement the <code>EventTarget</code> interface.</p>
- <p>There is a one-to-one mapping from <code><a href=#window>Window</a></code> objects to
- <code><a href=#applicationcache>ApplicationCache</a></code> objects. The <dfn id=dom-applicationcache title=dom-applicationCache><code>applicationCache</code></dfn>
+ <p>There is a one-to-one mapping from <a href=#cache-host title="cache host">cache
+ hosts</a> to <code><a href=#applicationcache>ApplicationCache</a></code> objects. The <dfn id=dom-applicationcache title=dom-applicationCache><code>applicationCache</code></dfn>
attribute on <code><a href=#window>Window</a></code> objects must return the
<code><a href=#applicationcache>ApplicationCache</a></code> object associated with the
- <code><a href=#window>Window</a></code> object.</p>
+ <code><a href=#window>Window</a></code> object's <a href=#active-document>active document</a>. The <dfn id=dom-worker-applicationcache title=dom-worker-applicationCache><code>applicationCache</code></dfn>
+ attribute on <code>SharedWorkerGlobalScope</code> objects must
+ return the <code><a href=#applicationcache>ApplicationCache</a></code> object associated with the
+ worker.</p>
- <p>An <code><a href=#applicationcache>ApplicationCache</a></code> object might be associated with
- an <a href=#application-cache>application cache</a>. When the <code>Document</code>
- object that the <code><a href=#applicationcache>ApplicationCache</a></code> object maps to is
- associated with an application cache, then that is the application
- cache with which the <code><a href=#applicationcache>ApplicationCache</a></code> object is
- associated.</p>
-
<p>The <dfn id=dom-appcache-status title=dom-appcache-status><code>status</code></dfn>
attribute, on getting, must return the current state of the
- <a href=#application-cache>application cache</a> <code><a href=#applicationcache>ApplicationCache</a></code> object
- is associated with, if any. This must be the appropriate value from
- the following list:</p>
+ <a href=#application-cache>application cache</a> that the
+ <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache host</a> is
+ associated with, if any. This must be the appropriate value from the
+ following list:</p>
</div>
<dl><dt><dfn id=dom-appcache-uncached title=dom-appcache-UNCACHED><code>UNCACHED</code></dfn>
(numeric value 0)</dt>
- <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is not associated
- with an <a href=#application-cache>application cache</a> at this time.</dd>
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache
+ host</a> is not associated with an <a href=#application-cache>application
+ cache</a> at this time.</dd>
<dt><dfn id=dom-appcache-idle title=dom-appcache-IDLE><code>IDLE</code></dfn>
(numeric value 1)</dt>
- <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
- an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
- group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update
- status</a> is <i>idle</i>, and that <a href=#application-cache>application
- cache</a> is the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> cache in its
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache
+ host</a> is associated with an <a href=#application-cache>application cache</a>
+ whose <a href=#application-cache-group>application cache group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update status</a> is
+ <i>idle</i>, and that <a href=#application-cache>application cache</a> is the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> cache in its
<a href=#application-cache-group>application cache group</a>, and the <a href=#application-cache-group>application
cache group</a> is not marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>.</dd>
<dt><dfn id=dom-appcache-checking title=dom-appcache-CHECKING><code>CHECKING</code></dfn>
(numeric value 2)</dt>
- <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
- an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
- group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update
- status</a> is <i>checking</i>.</dd>
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache
+ host</a> is associated with an <a href=#application-cache>application cache</a>
+ whose <a href=#application-cache-group>application cache group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update status</a> is
+ <i>checking</i>.</dd>
<dt><dfn id=dom-appcache-downloading title=dom-appcache-DOWNLOADING><code>DOWNLOADING</code></dfn>
(numeric value 3)</dt>
- <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
- an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
- group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update
- status</a> is <i>downloading</i>.</dd>
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache
+ host</a> is associated with an <a href=#application-cache>application cache</a>
+ whose <a href=#application-cache-group>application cache group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update status</a> is
+ <i>downloading</i>.</dd>
<dt><dfn id=dom-appcache-updateready title=dom-appcache-UPDATEREADY><code>UPDATEREADY</code></dfn>
(numeric value 4)</dt>
- <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
- an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
- group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update
- status</a> is <i>idle</i>, and whose <a href=#application-cache-group>application cache
- group</a> is not marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, but that
- <a href=#application-cache>application cache</a> is <em>not</em> the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> cache in its
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache
+ host</a> is associated with an <a href=#application-cache>application cache</a>
+ whose <a href=#application-cache-group>application cache group</a>'s <a href=#concept-appcache-status title=concept-appcache-status>update status</a> is
+ <i>idle</i>, and whose <a href=#application-cache-group>application cache group</a> is not
+ marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>,
+ but that <a href=#application-cache>application cache</a> is <em>not</em> the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> cache in its
group.</dd>
<dt><dfn id=dom-appcache-obsolete title=dom-appcache-OBSOLETE><code>OBSOLETE</code></dfn>
(numeric value 5)</dt>
- <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object is associated with
- an <a href=#application-cache>application cache</a> whose <a href=#application-cache-group>application cache
- group</a> is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>.</dd>
+ <dd><p>The <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache
+ host</a> is associated with an <a href=#application-cache>application cache</a>
+ whose <a href=#application-cache-group>application cache group</a> is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>.</dd>
</dl><div class=impl>
<hr><p>If the <dfn id=dom-appcache-update title=dom-appcache-update><code>update()</code></dfn> method is
invoked, the user agent must invoke the <a href=#application-cache-update-process>application cache
update process</a>, in the background, for the <a href=#application-cache>application
- cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object is
- associated, but with no <a href=#browsing-context>browsing context</a>. If there is
- no such application cache, or if it is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then the method
+ cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object's
+ <a href=#cache-host>cache host</a> is associated, but without giving that
+ <a href=#cache-host>cache host</a> to the algorithm. If there is no such
+ <a href=#application-cache>application cache</a>, or if it is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then the method
must raise an <code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception instead.</p>
<p>If the <dfn id=dom-appcache-swapcache title=dom-appcache-swapCache><code>swapCache()</code></dfn> method
is invoked, the user agent must run the following steps:
- <ol><li><p>Let <var title="">document</var> be the
- <code>Document</code> with which the <code><a href=#applicationcache>ApplicationCache</a></code>
- object is associated.</li>
-
- <li><p>Check that <var title="">document</var> is associated with
- an <a href=#application-cache>application cache</a>. If it is not, then raise an
+ <ol><li><p>Check that <code><a href=#applicationcache>ApplicationCache</a></code> object's
+ <a href=#cache-host>cache host</a> is associated with an <a href=#application-cache>application
+ cache</a>. If it is not, then raise an
<code><a href=#invalid_state_err>INVALID_STATE_ERR</a></code> exception and abort these
steps.</li>
<li><p>Let <var title="">cache</var> be the <a href=#application-cache>application
- cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object is
- associated. (By definition, this is the same as the one that was
- found in the previous step.)</li>
+ cache</a> with which the <code><a href=#applicationcache>ApplicationCache</a></code> object's
+ <a href=#cache-host>cache host</a> is associated. (By definition, this is the
+ same as the one that was found in the previous step.)</li>
<li><p>If <var title="">cache</var>'s <a href=#application-cache-group>application cache
group</a> is marked as <a href=#concept-appcache-obsolete title=concept-appcache-obsolete>obsolete</a>, then unassociate
- <var title="">document</var> from <var title="">cache</var> and
- abort these steps. (Resources will now load from the network
- instead of the cache.)</li>
+ the <code><a href=#applicationcache>ApplicationCache</a></code> object's <a href=#cache-host>cache host</a>
+ from <var title="">cache</var> and abort these steps. (Resources
+ will now load from the network instead of the cache.)</li>
<li><p>Check that there is an application cache in the same
<a href=#application-cache-group>application cache group</a> as <var title="">cache</var>
@@ -43504,7 +43521,9 @@
<var title="">cache</var> whose <a href=#concept-appcache-completeness title=concept-appcache-completeness>completeness flag</a> is
<i>complete</i>.</li>
- <li><p>Unassociate <var title="">document</var> from <var title="">cache</var> and instead associate it with <var title="">new cache</var>.</li>
+ <li><p>Unassociate the <code><a href=#applicationcache>ApplicationCache</a></code> object's
+ <a href=#cache-host>cache host</a> from <var title="">cache</var> and instead
+ associate it with <var title="">new cache</var>.</li>
</ol><p>The following are the <a href=#event-handler-attributes-0>event handler attributes</a> that
must be supported, as DOM attributes, by all objects implementing
Modified: source
===================================================================
--- source 2009-03-27 00:48:17 UTC (rev 2918)
+++ source 2009-03-28 00:35:07 UTC (rev 2919)
@@ -47867,13 +47867,26 @@
<hr>
+ <p>A <dfn>cache host</dfn> is a <code>Document</code> or a
+ <code>SharedWorkerGlobalScope</code> object. A <span>cache
+ host</span> can be associated with an <span>application
+ cache</span>.</p>
+
<p>A <code>Document</code> initially is not associated with an
- <span>application cache</span>, but steps <a
+ <span>application cache</span>, buu can become associated with one
+ early during the page load process, when steps <a
href="#parser-appcache">in the parser</a> and in the <span
- title="navigate">navigation</span> sections cause <span
- title="concept-appcache-init">cache selection</span> to occur early
- in the page load process.</p>
+ title="navigate">navigation</span> sections that cause <span
+ title="concept-appcache-init">cache selection</span> to occur.</p>
+ <p>A <code>SharedWorkerGlobalScope</code> is can be associated with
+ an <span>application cache</span> when it is created.</p>
+
+ <p>Each <span>cache host</span> has an associated
+ <code>ApplicationCache</code> object.</p>
+
+ <hr>
+
<p>Multiple <span title="application cache">application
caches</span> in different <span title="application cache
group">application cache groups</span> can contain the same
@@ -48358,7 +48371,7 @@
process</dfn> for an <span>absolute URL</span> purported to identify
a <span title="concept-appcache-manifest">manifest</span>, or for an
<span>application cache group</span>, potentially given a particular
- <span>browsing context</span>, and potentially given a new <span
+ <span>cache host</span>, and potentially given a new <span
title="concept-appcache-master">master</span> resource, the user
agent must run the following steps:</p>
@@ -48424,24 +48437,24 @@
title="concept-appcache-pending-masters">list of pending master
entries</span>.</p></li>
- <li><p>If these steps were invoked with a <span>browsing
- context</span>, and the <span
+ <li><p>If these steps were invoked with a <span>cache
+ host</span>, and the <span
title="concept-appcache-status">status</span> of <var
title="">cache group</var> is <i>checking</i> or
<i>downloading</i>, then <span>queue a task</span> to <span>fire
a simple event</span> called <code
title="event-checking">checking</code> at the
- <code>ApplicationCache</code> singleton of that <span>browsing
- context</span>.</p></li>
+ <code>ApplicationCache</code> singleton of that <span>cache
+ host</span>.</p></li>
- <li><p>If these steps were invoked with a <span>browsing
- context</span>, and the <span
+ <li><p>If these steps were invoked with a <span>cache
+ host</span>, and the <span
title="concept-appcache-status">status</span> of <var
title="">cache group</var> is <i>downloading</i>, then also
<span>queue a task</span> to <span>fire a simple event</span>
called <code title="event-downloading">downloading</code> at the
- <code>ApplicationCache</code> singleton of that <span>browsing
- context</span>.</p></li>
+ <code>ApplicationCache</code> singleton of that <span>cache
+ host</span>.</p></li>
<li><p>If the <span title="concept-appcache-status">status</span>
of the <var title="">cache group</var> is either <i>checking</i>
@@ -48452,13 +48465,12 @@
title="concept-appcache-status">status</span> of <var
title="">cache group</var> to <i>checking</i>.</p>
- <li><p>For each <span>browsing context</span> whose <span>active
- document</span> is associated with an <span>application
- cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-checking">checking</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
+ <li><p>For each <span>cache host</span> associated with an
+ <span>application cache</span> in <var title="">cache
+ group</var>, <span>queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-checking">checking</code>
+ at the <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user
that the user agent is checking for the availability of
updates.</p></li>
@@ -48476,12 +48488,11 @@
</li>
<li><p>If this is a <span title="concept-appcache-cache">cache
- attempt</span>, then this algorithm was invoked with a
- <span>browsing context</span>; <span>queue a task</span> to
- <span>fire a simple event</span> called <code
- title="event-checking">checking</code> at the
- <code>ApplicationCache</code> singleton of that <span>browsing
- context</span>.</p></li>
+ attempt</span>, then this algorithm was invoked with a <span>cache
+ host</span>; <span>queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-checking">checking</code> at
+ the <code>ApplicationCache</code> singleton of that <span>cache
+ host</span>.</p></li>
<li>
@@ -48517,13 +48528,12 @@
associated with an <span>application cache</span> in the <var
title="">cache group</var>.</p></li>
- <li><p>For each <span>browsing context</span> whose <span>active
- document</span> is associated with an <span>application
- cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-obsolete">obsolete</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
+ <li><p>For each <span>cache host</span> associated with an
+ <span>application cache</span> in <var title="">cache
+ group</var>, <span>queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-obsolete">obsolete</code>
+ at the <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user
that the application is no longer available for offline
use.</p></li>
@@ -48533,12 +48543,12 @@
entries</span>, <span>queue a task</span> to <span>fire a simple
event</span> called <code title="event-error">error</code> (not
<code title="event-obsolete">obsolete</code>!) at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span> whose <span>active document</span> is the
- <code>Document</code> for this entry, if there still is one. The
- default action of this event should be the display of some sort
- of user interface indicating to the user that the user agent
- failed to save the application for offline use.</p></li>
+ <code>ApplicationCache</code> singleton of the <span>cache
+ host</span> the <code>Document</code> for this entry, if there
+ still is one. The default action of this event should be the
+ display of some sort of user interface indicating to the user
+ that the user agent failed to save the application for offline
+ use.</p></li>
<li><p>If <var title="">cache group</var> has an
<span>application cache</span> whose <span
@@ -48601,12 +48611,12 @@
user cancels the download), then <span>queue a task</span> to
<span>fire a simple event</span> called <code
title="event-error">error</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span> whose <span>active document</span> is the
- <code>Document</code> for this entry, if there still is one. The
- default action of this event should be the display of some sort
- of user interface indicating to the user that the user agent
- failed to save the application for offline use.</p>
+ <code>ApplicationCache</code> singleton of the <span>cache
+ host</span> the <code>Document</code> for this entry, if there
+ still is one. The default action of this event should be the
+ display of some sort of user interface indicating to the user
+ that the user agent failed to save the application for offline
+ use.</p>
<p>Otherwise, associate the <code>Document</code> for this entry
with <var title="">cache</var>; store the resource for this
@@ -48621,13 +48631,12 @@
</li>
- <li><p>For each <span>browsing context</span> whose <span>active
- document</span> is associated with an <span>application
- cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-noupdate">noupdate</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
+ <li><p>For each <span>cache host</span> associated with an
+ <span>application cache</span> in <var title="">cache
+ group</var>, <span>queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-noupdate">noupdate</code>
+ at the <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user
that the application is up to date.</p></li>
@@ -48662,13 +48671,12 @@
<li><p>Set the <span title="concept-appcache-status">status</span>
of <var title="">cache group</var> to <i>downloading</i>.</p></li>
- <li><p>For each <span>browsing context</span> whose <span>active
- document</span> is associated with an <span>application
- cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-downloading">downloading</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
+ <li><p>For each <span>cache host</span> associated with an
+ <span>application cache</span> in <var title="">cache group</var>,
+ <span>queue a task</span> to <span>fire a simple event</span>
+ called <code title="event-downloading">downloading</code> at the
+ <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user that
a new version is being downloaded.</p></li>
@@ -48720,13 +48728,12 @@
</li>
- <li><p>For each <span>browsing context</span> whose <span>active
- document</span> is associated with an <span>application
- cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-progress">progress</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
+ <li><p>For each <span>cache host</span> associated with an
+ <span>application cache</span> in <var title="">cache
+ group</var>, <span>queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-progress">progress</code>
+ at the <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user
that a file is being downloaded in preparation for updating the
application.</p></li> <!-- XXX need to include progress
@@ -48876,10 +48883,9 @@
<li><p>Unassociate the <code>Document</code> for this entry from
<var title="">new cache</var>.</p></li>
- <li><p><span>Queue a task</span> to <span>fire a simple event</span>
- called <code title="event-error">error</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span> whose <span>active document</span> is the
+ <li><p><span>Queue a task</span> to <span>fire a simple
+ event</span> called <code title="event-error">error</code> at the
+ <code>ApplicationCache</code> singleton of the
<code>Document</code> for this entry, if there still is one. The
default action of this event should be the display of some sort
of user interface indicating to the user that the user agent
@@ -48956,28 +48962,26 @@
<li>
<p>If this is a <span title="concept-appcache-cache">cache
- attempt</span>, then for each <span>browsing context</span>
- whose <span>active document</span> is associated with an
- <span>application cache</span> in <var title="">cache
+ attempt</span>, then for each <span>cache host</span> associated
+ with an <span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
event</span> called <code title="event-cached">cached</code> at
- the <code>ApplicationCache</code> singleton of the
- <span>browsing context</span>. The default action of these
- events should be the display of some sort of user interface
- indicating to the user that the application has been cached and
- that they can now use it offline.</p>
+ the <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
+ display of some sort of user interface indicating to the user that
+ the application has been cached and that they can now use it
+ offline.</p>
<p>Otherwise, it is an <span
- title="concept-appcache-upgrade">upgrade attempt</span>. For
- each <span>browsing context</span> whose <span>active
- document</span> is associated with an <span>application
+ title="concept-appcache-upgrade">upgrade attempt</span>. For each
+ <span>cache host</span> associated with an <span>application
cache</span> in <var title="">cache group</var>, <span>queue a
task</span> to <span>fire a simple event</span> called <code
title="event-updateready">updateready</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
- display of some sort of user interface indicating to the user
- that a new version is available and that they can activate it by
+ <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
+ display of some sort of user interface indicating to the user that
+ a new version is available and that they can activate it by
reloading the page.</p>
</li>
@@ -49012,8 +49016,7 @@
<li><p><span>Queue a task</span> to <span>fire a simple
event</span> called <code title="event-error">error</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span> whose <span>active document</span> is the
+ <code>ApplicationCache</code> singleton of the
<code>Document</code> for this entry, if there still is one. The
default action of these events should be the display of some sort
of user interface indicating to the user that the user agent
@@ -49023,13 +49026,12 @@
</li>
- <li><p>For each <span>browsing context</span> whose <span>active
- document</span> is still associated with an <span>application
- cache</span> in <var title="">cache group</var>, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
- title="event-error">error</code> at the
- <code>ApplicationCache</code> singleton of the <span>browsing
- context</span>. The default action of these events should be the
+ <li><p>For each <span>cache host</span> still associated with an
+ <span>application cache</span> in <var title="">cache group</var>,
+ <span>queue a task</span> to <span>fire a simple event</span>
+ called <code title="event-error">error</code> at the
+ <code>ApplicationCache</code> singleton of the <span>cache
+ host</span>. The default action of these events should be the
display of some sort of user interface indicating to the user that
the user agent failed to save the application for offline
use.</p></li>
@@ -49047,9 +49049,8 @@
<li><p>If appropriate, remove any user interface indicating that an
update for this cache is in progress.</p></li>
- <li><p>Let the <span
- title="concept-appcache-status">status</span> of <var
- title="">cache group</var> be <i>idle</i>.</p></li>
+ <li><p>Let the <span title="concept-appcache-status">status</span>
+ of <var title="">cache group</var> be <i>idle</i>.</p></li>
<li><p>If this was a <span title="concept-appcache-cache">cache
attempt</span>, discard <var title="">cache group</var>
@@ -49068,9 +49069,9 @@
<p>User agents may invoke the <span>application cache update
process</span>, in the background, for any <span>application
- cache</span>, at any time (with no <span>browsing
- context</span>). This allows user agents to keep caches primed and
- to update caches even before the user visits a site.</p>
+ cache</span>, at any time (with no <span>cache host</span>). This
+ allows user agents to keep caches primed and to update caches even
+ before the user visits a site.</p>
@@ -49206,14 +49207,14 @@
<h5 id="changesToNetworkingModel">Changes to the networking model</h5>
- <p>When a <span>browsing context</span>'s <span>active
- document</span> is associated with an <span>application cache</span>
- whose <span title="concept-appcache-completeness">completeness
- flag</span> is <i>complete</i>, any and all loads for resources in
- that <span>browsing context</span> other than those for <span
- title="child browsing context">child browsing contexts</span> must
- go through the following steps instead of immediately invoking the
- mechanisms appropriate to that resource's scheme:</p>
+ <p>When a <span>cache host</span> is associated with an
+ <span>application cache</span> whose <span
+ title="concept-appcache-completeness">completeness flag</span> is
+ <i>complete</i>, any and all loads for resources related to that
+ <span>cache host</span> other than those for <span title="child
+ browsing context">child browsing contexts</span> must go through the
+ following steps instead of immediately invoking the mechanisms
+ appropriate to that resource's scheme:</p>
<ol>
@@ -49304,14 +49305,28 @@
<dl class="domintro">
- <dt><var title="">window</var> . <code title="dom-applicationCache">applicationCache</code> . <code title="dom-appcache-status">status</code></dt>
+ <dt><var title="">cache</var> = <var title="">window</var> . <code title="dom-applicationCache">applicationCache</code></dt>
<dd>
+ <p>(In a window.) Returns the <code>ApplicationCache</code> object that applies to the <span>active document</span> of that <code>Window</code>.</p>
+
+ </dd>
+
+ <dt><var title="">cache</var> = <var title="">self</var> . <code title="dom-applicationCache">applicationCache</code></dt>
+ <dd>
+
+ <p>(In a shared worker.) Returns the <code>ApplicationCache</code> object that applies to the current shared worker.</p>
+
+ </dd>
+
+ <dt><var title="">cache</var> . <code title="dom-appcache-status">status</code></dt>
+ <dd>
+
<p>Returns the current status of the application cache, as given by the constants defined below.</p>
</dd>
- <dt><var title="">window</var> . <code title="dom-applicationCache">applicationCache</code> . <code title="dom-appcache-update">update</code>()</dt>
+ <dt><var title="">cache</var> . <code title="dom-appcache-update">update</code>()</dt>
<dd>
<p>Invokes the application cache update process.</p>
@@ -49320,7 +49335,7 @@
</dd>
- <dt><var title="">window</var> . <code title="dom-applicationCache">applicationCache</code> . <code title="dom-appcache-swapCache">swapCache</code>()</dt>
+ <dt><var title="">cache</var> . <code title="dom-appcache-swapCache">swapCache</code>()</dt>
<dd>
<p>Switches to the most recent application cache, if there is a newer one. If there isn't, throws an <code>INVALID_ACCESS_ERR</code> exception.</p>
@@ -49334,25 +49349,23 @@
<p>Objects implementing the <code>ApplicationCache</code> interface
must also implement the <code>EventTarget</code> interface.</p>
- <p>There is a one-to-one mapping from <code>Window</code> objects to
- <code>ApplicationCache</code> objects. The <dfn
+ <p>There is a one-to-one mapping from <span title="cache host">cache
+ hosts</span> to <code>ApplicationCache</code> objects. The <dfn
title="dom-applicationCache"><code>applicationCache</code></dfn>
attribute on <code>Window</code> objects must return the
<code>ApplicationCache</code> object associated with the
- <code>Window</code> object.</p>
+ <code>Window</code> object's <span>active document</span>. The <dfn
+ title="dom-worker-applicationCache"><code>applicationCache</code></dfn>
+ attribute on <code>SharedWorkerGlobalScope</code> objects must
+ return the <code>ApplicationCache</code> object associated with the
+ worker.</p>
- <p>An <code>ApplicationCache</code> object might be associated with
- an <span>application cache</span>. When the <code>Document</code>
- object that the <code>ApplicationCache</code> object maps to is
- associated with an application cache, then that is the application
- cache with which the <code>ApplicationCache</code> object is
- associated.</p>
-
<p>The <dfn title="dom-appcache-status"><code>status</code></dfn>
attribute, on getting, must return the current state of the
- <span>application cache</span> <code>ApplicationCache</code> object
- is associated with, if any. This must be the appropriate value from
- the following list:</p>
+ <span>application cache</span> that the
+ <code>ApplicationCache</code> object's <span>cache host</span> is
+ associated with, if any. This must be the appropriate value from the
+ following list:</p>
</div>
@@ -49361,17 +49374,18 @@
<dt><dfn title="dom-appcache-UNCACHED"><code>UNCACHED</code></dfn>
(numeric value 0)</dt>
- <dd><p>The <code>ApplicationCache</code> object is not associated
- with an <span>application cache</span> at this time.</p></dd>
+ <dd><p>The <code>ApplicationCache</code> object's <span>cache
+ host</span> is not associated with an <span>application
+ cache</span> at this time.</p></dd>
<dt><dfn title="dom-appcache-IDLE"><code>IDLE</code></dfn>
(numeric value 1)</dt>
- <dd><p>The <code>ApplicationCache</code> object is associated with
- an <span>application cache</span> whose <span>application cache
- group</span>'s <span title="concept-appcache-status">update
- status</span> is <i>idle</i>, and that <span>application
- cache</span> is the <span
+ <dd><p>The <code>ApplicationCache</code> object's <span>cache
+ host</span> is associated with an <span>application cache</span>
+ whose <span>application cache group</span>'s <span
+ title="concept-appcache-status">update status</span> is
+ <i>idle</i>, and that <span>application cache</span> is the <span
title="concept-appcache-newer">newest</span> cache in its
<span>application cache group</span>, and the <span>application
cache group</span> is not marked as <span
@@ -49380,38 +49394,40 @@
<dt><dfn title="dom-appcache-CHECKING"><code>CHECKING</code></dfn>
(numeric value 2)</dt>
- <dd><p>The <code>ApplicationCache</code> object is associated with
- an <span>application cache</span> whose <span>application cache
- group</span>'s <span title="concept-appcache-status">update
- status</span> is <i>checking</i>.</p></dd>
+ <dd><p>The <code>ApplicationCache</code> object's <span>cache
+ host</span> is associated with an <span>application cache</span>
+ whose <span>application cache group</span>'s <span
+ title="concept-appcache-status">update status</span> is
+ <i>checking</i>.</p></dd>
<dt><dfn title="dom-appcache-DOWNLOADING"><code>DOWNLOADING</code></dfn>
(numeric value 3)</dt>
- <dd><p>The <code>ApplicationCache</code> object is associated with
- an <span>application cache</span> whose <span>application cache
- group</span>'s <span title="concept-appcache-status">update
- status</span> is <i>downloading</i>.</p></dd>
+ <dd><p>The <code>ApplicationCache</code> object's <span>cache
+ host</span> is associated with an <span>application cache</span>
+ whose <span>application cache group</span>'s <span
+ title="concept-appcache-status">update status</span> is
+ <i>downloading</i>.</p></dd>
<dt><dfn title="dom-appcache-UPDATEREADY"><code>UPDATEREADY</code></dfn>
(numeric value 4)</dt>
- <dd><p>The <code>ApplicationCache</code> object is associated with
- an <span>application cache</span> whose <span>application cache
- group</span>'s <span title="concept-appcache-status">update
- status</span> is <i>idle</i>, and whose <span>application cache
- group</span> is not marked as <span
- title="concept-appcache-obsolete">obsolete</span>, but that
- <span>application cache</span> is <em>not</em> the <span
+ <dd><p>The <code>ApplicationCache</code> object's <span>cache
+ host</span> is associated with an <span>application cache</span>
+ whose <span>application cache group</span>'s <span
+ title="concept-appcache-status">update status</span> is
+ <i>idle</i>, and whose <span>application cache group</span> is not
+ marked as <span title="concept-appcache-obsolete">obsolete</span>,
+ but that <span>application cache</span> is <em>not</em> the <span
title="concept-appcache-newer">newest</span> cache in its
group.</p></dd>
<dt><dfn title="dom-appcache-OBSOLETE"><code>OBSOLETE</code></dfn>
(numeric value 5)</dt>
- <dd><p>The <code>ApplicationCache</code> object is associated with
- an <span>application cache</span> whose <span>application cache
- group</span> is marked as <span
+ <dd><p>The <code>ApplicationCache</code> object's <span>cache
+ host</span> is associated with an <span>application cache</span>
+ whose <span>application cache group</span> is marked as <span
title="concept-appcache-obsolete">obsolete</span>.</p></dd>
</dl>
@@ -49424,9 +49440,10 @@
title="dom-appcache-update"><code>update()</code></dfn> method is
invoked, the user agent must invoke the <span>application cache
update process</span>, in the background, for the <span>application
- cache</span> with which the <code>ApplicationCache</code> object is
- associated, but with no <span>browsing context</span>. If there is
- no such application cache, or if it is marked as <span
+ cache</span> with which the <code>ApplicationCache</code> object's
+ <span>cache host</span> is associated, but without giving that
+ <span>cache host</span> to the algorithm. If there is no such
+ <span>application cache</span>, or if it is marked as <span
title="concept-appcache-obsolete">obsolete</span>, then the method
must raise an <code>INVALID_STATE_ERR</code> exception instead.</p>
@@ -49436,26 +49453,23 @@
<ol>
- <li><p>Let <var title="">document</var> be the
- <code>Document</code> with which the <code>ApplicationCache</code>
- object is associated.</p></li>
-
- <li><p>Check that <var title="">document</var> is associated with
- an <span>application cache</span>. If it is not, then raise an
+ <li><p>Check that <code>ApplicationCache</code> object's
+ <span>cache host</span> is associated with an <span>application
+ cache</span>. If it is not, then raise an
<code>INVALID_STATE_ERR</code> exception and abort these
steps.</p></li>
<li><p>Let <var title="">cache</var> be the <span>application
- cache</span> with which the <code>ApplicationCache</code> object is
- associated. (By definition, this is the same as the one that was
- found in the previous step.)</p></li>
+ cache</span> with which the <code>ApplicationCache</code> object's
+ <span>cache host</span> is associated. (By definition, this is the
+ same as the one that was found in the previous step.)</p></li>
<li><p>If <var title="">cache</var>'s <span>application cache
group</span> is marked as <span
title="concept-appcache-obsolete">obsolete</span>, then unassociate
- <var title="">document</var> from <var title="">cache</var> and
- abort these steps. (Resources will now load from the network
- instead of the cache.)</p></li>
+ the <code>ApplicationCache</code> object's <span>cache host</span>
+ from <var title="">cache</var> and abort these steps. (Resources
+ will now load from the network instead of the cache.)</p></li>
<li><p>Check that there is an application cache in the same
<span>application cache group</span> as <var title="">cache</var>
@@ -49473,9 +49487,9 @@
title="concept-appcache-completeness">completeness flag</span> is
<i>complete</i>.</p></li>
- <li><p>Unassociate <var title="">document</var> from <var
- title="">cache</var> and instead associate it with <var
- title="">new cache</var>.</p></li>
+ <li><p>Unassociate the <code>ApplicationCache</code> object's
+ <span>cache host</span> from <var title="">cache</var> and instead
+ associate it with <var title="">new cache</var>.</p></li>
</ol>
More information about the Commit-Watchers
mailing list