- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 16 Jun 2009 22:56:47 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv18317
Modified Files:
Overview.html
Log Message:
Mention the weirdness with <object> and appcache explicitly. (whatwg r3286)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2432
retrieving revision 1.2433
diff -u -d -r1.2432 -r1.2433
--- Overview.html 16 Jun 2009 19:57:03 -0000 1.2432
+++ Overview.html 16 Jun 2009 22:56:44 -0000 1.2433
@@ -16212,10 +16212,12 @@
to the value of this attribute; otherwise, the <a href="#browsing-context-name">browsing
context name</a> must be set to the empty string.</p>
- <p class="XXX">navigation might end up treating it as
- something else, because it can do sniffing. how should we
- handle that? it could also refetch the resource entirely,
- maybe from another application cache.</p>
+ <p class="note">It's possible that the <a href="#navigate" title="navigate">navigation</a> of the <a href="#browsing-context">browsing
+ context</a> will actually obtain the resource from a
+ different <a href="#application-cache">application cache</a>. Even if the resource
+ is then found to have a different type, it is still used as
+ part of a <a href="#nested-browsing-context">nested browsing context</a>; this algorithm
+ doesn't restart with the new resource.</p>
<!-- note that malformed XML files don't cause fallback -->
Received on Tuesday, 16 June 2009 22:56:53 UTC