[html5] r1044 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2007-10-11 13:58:35 -0700 (Thu, 11 Oct 2007)
New Revision: 1044

Modified:
   index
   source
Log:
[e] (0) Move broad requirements to after the specific requirements in the manifest syntax section.

Modified: index
===================================================================
--- index	2007-10-11 20:54:54 UTC (rev 1043)
+++ index	2007-10-11 20:58:35 UTC (rev 1044)
@@ -26108,10 +26108,6 @@
    line, and the corresponding fallback page being the second URI. All the
    other pages to be cached must be listed in explicit sections.
 
-  <p>Relative URIs must be given relative to the manifest's own URI.
-
-  <p>URIs in manifests must not have fragment identifiers.
-
   <p><a href="#opportunistic"
    title=concept-appcache-oppcache-ns>Opportunistic caching namespaces</a>
    must have the <a href="#same-schemehostport">same scheme/host/port</a> as
@@ -26129,6 +26125,10 @@
    section. (URIs in the online whitelist section may match opportunistic
    caching namespaces, however.)
 
+  <p>Relative URIs must be given relative to the manifest's own URI.
+
+  <p>URIs in manifests must not have fragment identifiers.
+
   <h5 id=parsing0><span class=secno>4.6.3.2. </span>Parsing cache manifests</h5>
 
   <p>When a user agent is to <dfn id=parse>parse a manifest</dfn>, it means

Modified: source
===================================================================
--- source	2007-10-11 20:54:54 UTC (rev 1043)
+++ source	2007-10-11 20:58:35 UTC (rev 1044)
@@ -23732,11 +23732,6 @@
   URI. All the other pages to be cached must be listed in explicit
   sections.</p>
 
-  <p>Relative URIs must be given relative to the manifest's own
-  URI.</p>
-
-  <p>URIs in manifests must not have fragment identifiers.</p>
-
   <p><span title="concept-appcache-oppcache-ns">Opportunistic caching
   namespaces</span> must have the <span>same scheme/host/port</span>
   as the manifest itself.</p>
@@ -23755,7 +23750,12 @@
   fallback section. (URIs in the online whitelist section may match
   opportunistic caching namespaces, however.)</p>
 
+  <p>Relative URIs must be given relative to the manifest's own
+  URI.</p>
 
+  <p>URIs in manifests must not have fragment identifiers.</p>
+
+
   <h5>Parsing cache manifests</h5>
 
   <p>When a user agent is to <dfn>parse a manifest</dfn>, it means