Skip to content

Commit

Permalink
[gw] (2) Make <iframe>s not inherit the cache of their parent.
Browse files Browse the repository at this point in the history 
git-svn-id: http://svn.whatwg.org/webapps@2414 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Nov 18, 2008
1 parent eef04d0 commit 8192959
Show file tree
Hide file tree
Showing 2 changed files with 33 additions and 94 deletions.
61 changes: 16 additions & 45 deletions index
View file
Expand Up @@ -35384,7 +35384,7 @@ style/default.css</pre>

</div>

<p>When the <dfn id=concept-appcache-init-with-attribute title=concept-appcache-init-with-attribute>application cache
<hr><p>When the <dfn id=concept-appcache-init-with-attribute title=concept-appcache-init-with-attribute>application cache
selection algorithm</dfn> algorithm is invoked with a manifest URL,
the user agent must run the first applicable set of steps from the
following list:</p>
Expand All @@ -35393,7 +35393,9 @@ style/default.css</pre>
<a href=#browsing-context>browsing context</a></dt>

<dd>

<p>Do nothing.</p>

</dd>


Expand Down Expand Up @@ -35465,51 +35467,23 @@ style/default.css</pre>
</dd>

</dl><p>When the <dfn id=concept-appcache-init-no-attribute title=concept-appcache-init-no-attribute>application cache
selection algorithm</dfn> is invoked <em>without</em> a manifest,
then the user agent must run the first applicable set of steps from
the following list:</p>

<dl><dt>If the resource is being loaded as part of navigation of a
<a href=#browsing-context>browsing context</a>, and the resource was fetched from a
particular <a href=#application-cache>application cache</a></dt>

<dd>
selection algorithm</dfn> is invoked <em>without</em> a manifest, if
the resource is being loaded as part of navigation of a
<a href=#browsing-context>browsing context</a>, and the resource was fetched from a
particular <a href=#application-cache>application cache</a>, then the user agent must
associate the <code>Document</code> with that application cache and
invoke the <a href=#application-cache-update-process>application cache update process</a> for that
cache, with that <a href=#browsing-context>browsing context</a>. Otherwise, nothing
special happens.</p>

<!-- this can only happen for subframes -->

<p>The user agent must associate the <code>Document</code> with
that application cache and invoke the <a href=#application-cache-update-process>application cache
update process</a> for that cache, with that <a href=#browsing-context>browsing
context</a>.</p>

</dd>

<dt>If the resource is being loaded as part of navigation of a
<a href=#child-browsing-context>child browsing context</a></dt>

<dd>

<!-- e.g. iframes to online whitelisted resources -->

<p>The user agent must associate the <code>Document</code> with
that application cache associated with the <a href=#active-document>active
document</a> of the <a href=#parent-browsing-context>parent browsing context</a>.</p>

</dd>

<dt>Otherwise</dt>

<dd>

<p>Nothing special happens with respect to application caches.</p>

</dd>

</dl><h5 id=changesToNetworkingModel><span class=secno>5.7.5.1 </span>Changes to the networking model</h5>
<h5 id=changesToNetworkingModel><span class=secno>5.7.5.1 </span>Changes to the networking model</h5>

<p>When a <a href=#browsing-context>browsing context</a> is associated with an
<a href=#application-cache>application cache</a>, any and all resource loads must go
through the following steps instead of immediately invoking the
<a href=#application-cache>application cache</a>, 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>

<ol><li><p>If the resource is not to be fetched using the HTTP GET
Expand Down Expand Up @@ -35604,10 +35578,7 @@ style/default.css</pre>
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. Otherwise, the <code><a href=#applicationcache>ApplicationCache</a></code> object is
associated with the application cache that the <code>Document</code>
object's <a href=#browsing-context>browsing context</a> is associated with, if
any.</p>
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
Expand Down
66 changes: 17 additions & 49 deletions source
View file
Expand Up @@ -40240,6 +40240,8 @@ style/default.css</pre>

</div>

<hr>

<p>When the <dfn
title="concept-appcache-init-with-attribute">application cache
selection algorithm</dfn> algorithm is invoked with a manifest URL,
Expand All @@ -40252,7 +40254,9 @@ style/default.css</pre>
<span>browsing context</span></dt>

<dd>

<p>Do nothing.</p>

</dd>


Expand Down Expand Up @@ -40335,57 +40339,24 @@ style/default.css</pre>

<p>When the <dfn
title="concept-appcache-init-no-attribute">application cache
selection algorithm</dfn> is invoked <em>without</em> a manifest,
then the user agent must run the first applicable set of steps from
the following list:</p>

<dl>

<dt>If the resource is being loaded as part of navigation of a
<span>browsing context</span>, and the resource was fetched from a
particular <span>application cache</span></dt>

<dd>

<!-- this can only happen for subframes -->

<p>The user agent must associate the <code>Document</code> with
that application cache and invoke the <span>application cache
update process</span> for that cache, with that <span>browsing
context</span>.</p>

</dd>

<dt>If the resource is being loaded as part of navigation of a
<span>child browsing context</span></dt>

<dd>

<!-- e.g. iframes to online whitelisted resources -->

<p>The user agent must associate the <code>Document</code> with
that application cache associated with the <span>active
document</span> of the <span>parent browsing context</span>.</p>

</dd>

<dt>Otherwise</dt>

<dd>

<p>Nothing special happens with respect to application caches.</p>

</dd>

</dl>
selection algorithm</dfn> is invoked <em>without</em> a manifest, if
the resource is being loaded as part of navigation of a
<span>browsing context</span>, and the resource was fetched from a
particular <span>application cache</span>, then the user agent must
associate the <code>Document</code> with that application cache and
invoke the <span>application cache update process</span> for that
cache, with that <span>browsing context</span>. Otherwise, nothing
special happens.</p>



<h5 id="changesToNetworkingModel">Changes to the networking model</h5>

<p>When a <span>browsing context</span> is associated with an
<span>application cache</span>, any and all resource loads must go
through the following steps instead of immediately invoking the
<span>application cache</span>, 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>

<ol>
Expand Down Expand Up @@ -40490,10 +40461,7 @@ style/default.css</pre>
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. Otherwise, the <code>ApplicationCache</code> object is
associated with the application cache that the <code>Document</code>
object's <span>browsing context</span> is associated with, if
any.</p>
associated.</p>

<p>The <dfn title="dom-appcache-status"><code>status</code></dfn>
attribute, on getting, must return the current state of the
Expand Down

0 comments on commit 8192959

Please sign in to comment.