- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 18 Nov 2008 04:06:04 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv13363
Modified Files:
Overview.html
Log Message:
Make <iframe>s not inherit the cache of their parent. (whatwg r2414)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1585
retrieving revision 1.1586
diff -u -d -r1.1585 -r1.1586
--- Overview.html 18 Nov 2008 03:40:57 -0000 1.1585
+++ Overview.html 18 Nov 2008 04:06:01 -0000 1.1586
@@ -28747,14 +28747,16 @@
<!-- "resolve a url" canonicalises the case for the scheme and host
and removes the port if it is the default -->
- </div><p>When the <dfn id=concept-appcache-init-with-attribute title=concept-appcache-init-with-attribute>application cache
+ </div><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:<dl class=switch><dt>If the resource is not being loaded as part of navigation of a
<a href=#browsing-context>browsing context</a></dt>
<dd>
+
<p>Do nothing.</p>
+
</dd>
@@ -28826,47 +28828,17 @@
</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:<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>
-
- <!-- 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><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
+ 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.<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 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:<ol><li><p>If the resource is not to be fetched using the HTTP GET
mechanism or equivalent, then <a href=#fetch>fetch</a> the resource
normally and abort these steps.</li>
@@ -28948,10 +28920,7 @@
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>The <dfn id=dom-appcache-status title=dom-appcache-status><code>status</code></dfn>
+ associated.<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
Received on Tuesday, 18 November 2008 04:06:14 UTC