W3C home > Mailing lists > Public > public-html-commits@w3.org > August 2009

html5/spec Overview.html,1.2796,1.2797

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 14 Aug 2009 00:29:20 +0000
To: public-html-commits@w3.org
Message-Id: <E1MbkfY-0007Op-Gq@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv28429

Modified Files:
	Overview.html 
Log Message:
appcache: Always allow cross-scheme networking to work unaffected. Clarify rules about syntax of manifests regarding schemes and the like. (whatwg r3606)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2796
retrieving revision 1.2797
diff -u -d -r1.2796 -r1.2797
--- Overview.html	14 Aug 2009 00:01:00 -0000	1.2796
+++ Overview.html	14 Aug 2009 00:29:16 -0000	1.2797
@@ -45117,10 +45117,10 @@
 # here is another set of files to cache, this time just the CSS file.
 CACHE:
 style/default.css</pre><h5 id="writing-cache-manifests"><span class="secno">6.9.3.2 </span>Writing cache manifests</h5><p>Manifests must be served using the
-  <code><a href="#text-cache-manifest">text/cache-manifest</a></code> <a href="#mime-type">MIME type</a>. All resources served
-  using the <code><a href="#text-cache-manifest">text/cache-manifest</a></code> <a href="#mime-type">MIME type</a> must follow the
-  syntax of application cache manifests, as described in this
-  section.<p>An application cache manifest is a text file, whose text is
+  <code><a href="#text-cache-manifest">text/cache-manifest</a></code> <a href="#mime-type">MIME type</a>. All
+  resources served using the <code><a href="#text-cache-manifest">text/cache-manifest</a></code>
+  <a href="#mime-type">MIME type</a> must follow the syntax of application cache
+  manifests, as described in this section.<p>An application cache manifest is a text file, whose text is
   encoded using UTF-8. Data in application cache manifests is
   line-based. Newlines must be represented by U+000A LINE FEED (LF)
   characters, U+000D CARRIAGE RETURN (CR) characters, or U+000D
@@ -45182,10 +45182,16 @@
     <p>The format that data lines must take depends on the current
     section.</p>
 
-    <p>When the current section is the explicit section or the online
-    whitelist section, data lines must consist of zero or more U+0020
-    SPACE and U+0009 CHARACTER TABULATION (tab) characters, either a
-    single U+002A ASTERISK character (*) <!--
+    <p>When the current section is the explicit section, data lines
+    must consist of zero or more U+0020 SPACE and U+0009 CHARACTER
+    TABULATION (tab) characters, a <a href="#valid-url">valid URL</a> identifying
+    a resource other than the manifest itself, and then zero or more
+    U+0020 SPACE and U+0009 CHARACTER TABULATION (tab) characters.</p>
+
+    <p>When the current section is the online whitelist section, data
+    lines must consist of zero or more U+0020 SPACE and U+0009
+    CHARACTER TABULATION (tab) characters, either a single U+002A
+    ASTERISK character (*) <!--
     concept-appcache-onlinewhitelist-wildcard --> or a <a href="#valid-url">valid
     URL</a> identifying a resource other than the manifest itself,
     and then zero or more U+0020 SPACE and U+0009 CHARACTER TABULATION
@@ -45219,7 +45225,9 @@
   in this way, a U+002A ASTERISK character (*) character may be
   specified as one of the URLs. <!--
   concept-appcache-onlinewhitelist-wildcard --><p>Relative URLs must be given relative to the manifest's own
-  URL.<p>URLs in manifests must not have fragment identifiers (i.e. the
+  URL. All URLs in the manifest must have the same <a href="#url-scheme" title="url-scheme">&lt;scheme&gt;</a> as the manifest itself
+  (either explicitly or implicitly, through the use of relative
+  URLs).<p>URLs in manifests must not have fragment identifiers (i.e. the
   U+0023 NUMBER SIGN character isn't allowed in URLs in
   manifests).<div class="impl">
 
@@ -46216,8 +46224,8 @@
 
   <ol><li><p>If the resource is not to be fetched using the HTTP GET
    mechanism <a href="#concept-http-equivalent-get" title="concept-http-equivalent-get">or
-   equivalent</a>, or if it has a <a href="#javascript-protocol" title="javascript
-   protocol"><code title="">javascript:</code> URL</a>, then
+   equivalent</a>, or if its <a href="#url">URL</a> has a different <a href="#url-scheme" title="url-scheme">&lt;scheme&gt;</a> component than the
+   <a href="#application-cache">application cache</a>'s <a href="#concept-appcache-manifest" title="concept-appcache-manifest">manifest</a>, then
    <a href="#fetch">fetch</a> the resource normally and abort these
    steps.</li>
 
Received on Friday, 14 August 2009 00:29:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 August 2009 00:29:32 GMT