[html5] r3286 - [e] (0) Mention the weirdness with <object> and appcache explicitly.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-16 15:56:38 -0700 (Tue, 16 Jun 2009)
New Revision: 3286

Modified:
   index
   source
Log:
[e] (0) Mention the weirdness with <object> and appcache explicitly.

Modified: index
===================================================================
--- index	2009-06-16 19:56:57 UTC (rev 3285)
+++ index	2009-06-16 22:56:38 UTC (rev 3286)
@@ -18723,10 +18723,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 -->
 

Modified: source
===================================================================
--- source	2009-06-16 19:56:57 UTC (rev 3285)
+++ source	2009-06-16 22:56:38 UTC (rev 3286)
@@ -19964,10 +19964,13 @@
         to the value of this attribute; otherwise, the <span>browsing
         context name</span> 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 <span
+        title="navigate">navigation</span> of the <span>browsing
+        context</span> will actually obtain the resource from a
+        different <span>application cache</span>. Even if the resource
+        is then found to have a different type, it is still used as
+        part of a <span>nested browsing context</span>; this algorithm
+        doesn't restart with the new resource.</p>
 
         <!-- note that malformed XML files don't cause fallback -->