Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[gw] (2) When getting the manifest fails, don't associate the resourc…
…e with the cache, since the resource is probably screwed up / too new / a captive portal anyway.

git-svn-id: http://svn.whatwg.org/webapps@2696 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 23, 2009
1 parent 53a1ff5 commit f888f9b
Show file tree
Hide file tree
Showing 2 changed files with 40 additions and 53 deletions.
45 changes: 20 additions & 25 deletions index
Expand Up @@ -37228,7 +37228,7 @@ style/default.css</pre>
or the server reported it as "304 Not Modified" <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>, then
run these substeps:</p>

<ol><!-- XXX can they be merged with the cache failure steps? (event name is different, anything else?) --><li><p>Let <var title="">cache</var> be the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> <a href=#application-cache>application
<ol><li><p>Let <var title="">cache</var> be the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> <a href=#application-cache>application
cache</a> in <var title="">cache group</var>.</li>

<li>
Expand Down Expand Up @@ -37354,10 +37354,12 @@ style/default.css</pre>
<li>

<p><a href=#fetch>Fetch</a> the resource. If this is an <a href=#concept-appcache-upgrade title=concept-appcache-upgrade>upgrade attempt</a>, then
use <var title="">cache</var> as an HTTP cache, and honor HTTP
caching semantics (such as expiration, ETags, and so forth) with
respect to that cache. User agents may also have other caches in
place that are also honored.</p>
use the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a>
<a href=#application-cache>application cache</a> in <var title="">cache
group</var> as an HTTP cache, and honor HTTP caching semantics
(such as expiration, ETags, and so forth) with respect to that
cache. User agents may also have other caches in place that are
also honored.</p>

<p class=note>If the resource in question is already being
downloaded for other reasons then the existing download process
Expand Down Expand Up @@ -37618,9 +37620,6 @@ style/default.css</pre>
that the user agent failed to save the application for offline
use.</li>

<li><p>Let <var title="">cache</var> be the <a href=#concept-appcache-newer title=concept-appcache-newer>newest</a> <a href=#application-cache>application
cache</a> in <var title="">cache group</var>.</li>

<li>

<p>For each entry in <var title="">cache group</var>'s <a href=#concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
Expand All @@ -37630,21 +37629,17 @@ style/default.css</pre>
<ol><li><p>Wait for the resource for this entry to have completely
downloaded.</p>

<li><p>If the download was successful, associate the
<code>Document</code> for this entry with <var title="">cache</var> (unassociating it from the other
<a href=#application-cache>application cache</a> it is associated with, if any),
store the resource for this entry in <var title="">cache</var>,
if it isn't already there, and categorize its entry as a <a href=#concept-appcache-master title=concept-appcache-master>master entry</a>.</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 <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><p>Unassociate the <code>Document</code> for this entry
from its <a href=#application-cache>application cache</a>.</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
<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>

</ol></li>

Expand All @@ -37653,7 +37648,7 @@ style/default.css</pre>

<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
<i>incomplete</i>, then discrad that <a href=#application-cache>application
<i>incomplete</i>, then discard that <a href=#application-cache>application
cache</a>.</p>

<li><p>If appropriate, remove any user interface indicating that
Expand Down Expand Up @@ -37710,7 +37705,7 @@ style/default.css</pre>

<p>When the <dfn id=concept-appcache-init title=concept-appcache-init>application cache
selection algorithm</dfn> algorithm is invoked with a
<code>Document</code> <var title="">document</var> and optinally a
<code>Document</code> <var title="">document</var> and optionally a
manifest <a href=#url>URL</a> <var title="">manifest URL</var>, the user
agent must run the first applicable set of steps from the following
list:</p>
Expand Down
48 changes: 20 additions & 28 deletions source
Expand Up @@ -42375,7 +42375,7 @@ style/default.css</pre>
title="concept-http-equivalent-codes">or equivalent</span>, then
run these substeps:</p>

<ol> <!-- XXX can they be merged with the cache failure steps? (event name is different, anything else?) -->
<ol>

<li><p>Let <var title="">cache</var> be the <span
title="concept-appcache-newer">newest</span> <span>application
Expand Down Expand Up @@ -42525,10 +42525,12 @@ style/default.css</pre>

<p><span>Fetch</span> the resource. If this is an <span
title="concept-appcache-upgrade">upgrade attempt</span>, then
use <var title="">cache</var> as an HTTP cache, and honor HTTP
caching semantics (such as expiration, ETags, and so forth) with
respect to that cache. User agents may also have other caches in
place that are also honored.</p>
use the <span title="concept-appcache-newer">newest</span>
<span>application cache</span> in <var title="">cache
group</var> as an HTTP cache, and honor HTTP caching semantics
(such as expiration, ETags, and so forth) with respect to that
cache. User agents may also have other caches in place that are
also honored.</p>

<p class="note">If the resource in question is already being
downloaded for other reasons then the existing download process
Expand Down Expand Up @@ -42832,10 +42834,6 @@ style/default.css</pre>
that the user agent failed to save the application for offline
use.</p></li>

<li><p>Let <var title="">cache</var> be the <span
title="concept-appcache-newer">newest</span> <span>application
cache</span> in <var title="">cache group</var>.</p></li>

<li>

<p>For each entry in <var title="">cache group</var>'s <span
Expand All @@ -42848,23 +42846,17 @@ style/default.css</pre>
<li><p>Wait for the resource for this entry to have completely
downloaded.</p>

<li><p>If the download was successful, associate the
<code>Document</code> for this entry with <var
title="">cache</var> (unassociating it from the other
<span>application cache</span> it is associated with, if any),
store the resource for this entry in <var title="">cache</var>,
if it isn't already there, and categorize its entry as a <span
title="concept-appcache-master">master entry</span>.</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 <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><p>Unassociate the <code>Document</code> for this entry
from its <span>application cache</span>.</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
<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>

</ol>

Expand All @@ -42877,7 +42869,7 @@ style/default.css</pre>
<li><p>If <var title="">cache group</var> has an
<span>application cache</span> whose <span
title="concept-appcache-completeness">completeness flag</span> is
<i>incomplete</i>, then discrad that <span>application
<i>incomplete</i>, then discard that <span>application
cache</span>.</p>

<li><p>If appropriate, remove any user interface indicating that
Expand Down Expand Up @@ -42946,7 +42938,7 @@ style/default.css</pre>

<p>When the <dfn title="concept-appcache-init">application cache
selection algorithm</dfn> algorithm is invoked with a
<code>Document</code> <var title="">document</var> and optinally a
<code>Document</code> <var title="">document</var> and optionally a
manifest <span>URL</span> <var title="">manifest URL</var>, the user
agent must run the first applicable set of steps from the following
list:</p>
Expand Down

0 comments on commit f888f9b

Please sign in to comment.