W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2009

spec/Overview.html 1.1979 2808 Allow HTML and XML files to be fetched f

From: poot <cvsmail@w3.org>
Date: Fri, 13 Feb 2009 11:37:52 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090213023752.E44902BC97@toro.w3.mag.keio.ac.jp>

Allow HTML and XML files to be fetched from an application cache despite
not having a manifest (same-origin caches only, of course). (whatwg
r2808)

5.8.6 The application cache selection algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#the-application-cache-selection-algorithm
application cache selection algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#concept-appcache-init
5.10.3 Page load processing model for XML files
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#read-xml
5.10.5 Page load processing model for images
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#read-image
5.10.6 Page load processing model for content that uses plugins
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#read-plugin
5.10.7 Page load processing model for inline content that doesn't have a DOM
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#read-ua-inline
If the Document is being loaded as part of navigation of a browsing context, then: if the newly created element has a manifest attribute, then resolve the value of that attribute to an absolute URL, relative to the newly created element, and if that is successful, run the application cache selection algorithm with the resulting absolute URL; otherwise, if there is no such attribute or resolving it fails, run the application cache selection algorithm with no manifest. The algorithm must be passed the Document object.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#parser-appcache
5.10.4 Page load processing model for text files
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1979.html#read-text

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1978&r2=1.1979&f=h
http://html5.org/tools/web-apps-tracker?from=2807&to=2808

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1978
retrieving revision 1.1979
diff -u -d -r1.1978 -r1.1979
--- Overview.html	13 Feb 2009 02:20:04 -0000	1.1978
+++ Overview.html	13 Feb 2009 02:34:37 -0000	1.1979
@@ -40913,19 +40913,14 @@
 
   <p>When the <dfn id=concept-appcache-init title=concept-appcache-init>application cache
   selection algorithm</dfn> algorithm is invoked with a
-  <code>Document</code> <var title="">document</var>, a flag <var title="">document-is-markup</var> which can be true or false, and
-  optionally a manifest <a href=#url>URL</a> <var title="">manifest
-  URL</var>, the user agent must run the first applicable set of steps
-  from the following list:</p>
+  <code>Document</code> <var title="">document</var> and optionally a
+  manifest <a href=#url>URL</a> <var title="">manifest URL</var>, the user
+  agent must run the first applicable set of steps from the following
+  list:</p>
 
   <dl class=switch>
 
-   <dt>If the flag <var title="">document-is-markup</var> is true, and
-   <var title="">document</var> was loaded from an <a href=#application-cache>application
-   cache</a>, and there is no <var title="">manifest URL</var></dt>
-
-   <dt>If the flag <var title="">document-is-markup</var> is true, If
-   <var title="">document</var> was loaded from an <a href=#application-cache>application
+   <dt>If there is a <var title="">manifest URL</var>, and <var title="">document</var> was loaded from an <a href=#application-cache>application
    cache</a>, and the URL of the <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a> of that cache's
    <a href=#application-cache-group>application cache group</a> is <em>not</em> the same as
    <var title="">manifest URL</var></dt>
@@ -40954,9 +40949,10 @@
 
 
    <dt>If <var title="">document</var> was loaded from an
-   <a href=#application-cache>application cache</a><!--[redundant], and the URL of the
-   <span title="concept-appcache-manifest">manifest</span> of that
-   cache's <span>application cache group</span> is the same as <var
+   <a href=#application-cache>application cache</a><!--[redundant], and either there is
+   no <var title="">manifest URL</var>, or the URL of the <span
+   title="concept-appcache-manifest">manifest</span> of the cache's
+   <span>application cache group</span> is the same as <var
    title="">manifest URL</var>--></dt>
 
    <dd>
@@ -40972,8 +40968,9 @@
    <dt>If <var title="">document</var> <!--[redundant] was not loaded
    from an <span>application cache</span>, but it--> was loaded using
    HTTP GET <a href=#concept-http-equivalent-get title=concept-http-equivalent-get>or
-   equivalent</a>, and <var title="">manifest URL</var> has the
-   <a href=#same-origin>same origin</a> as <var title="">document</var></dt>
+   equivalent</a>, and, there is a <var title="">manifest
+   URL</var>, and <var title="">manifest URL</var> has the <a href=#same-origin>same
+   origin</a> as <var title="">document</var></dt>
 
    <dd>
 
@@ -40984,7 +40981,8 @@
    </dd>
 
 
-   <dt>Otherwise</dt> <!-- not from cache and either non GET or wrong-origin manifest -->
+   <dt>Otherwise</dt> <!-- not from cache and either no <var
+   title="">manifest URL</var>, or non-GET, or wrong-origin manifest -->
 
    <dd>
 
@@ -42196,14 +42194,12 @@
   into the document</a>, the user agent must <a href=#resolve-a-url title="resolve a
   url">resolve</a> the value of that attribute relative to that
   element, and if that is successful, must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache selection
-  algorithm</a> with the <var title="">document-is-markup</var>
-  flag set to true, the resulting <a href=#absolute-url>absolute URL</a> as the
+  algorithm</a> with the resulting <a href=#absolute-url>absolute URL</a> as the
   manifest URL, and passing in the newly-created
   <code>Document</code>. Otherwise, if the attribute is absent or
   resolving it fails, then as soon as the root element is <a href=#insert-an-element-into-a-document title="insert an element into a document">inserted into the
   document</a>, the user agent must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache selection
-  algorithm</a> with the <var title="">document-is-markup</var>
-  flag set to true, no manifest, and passing in the
+  algorithm</a> with no manifest, and passing in the
   <code>Document</code>.</p>
 
   <p class=note>Because the processing of the <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute happens
@@ -42254,8 +42250,8 @@
 
   <p>Upon creation of the <code>Document</code> object, the user agent
   must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache
-  selection algorithm</a> with the <var title="">document-is-markup</var> flag set to false, no manifest,
-  and passing in the newly-created <code>Document</code>.</p>
+  selection algorithm</a> with no manifest, and passing in the
+  newly-created <code>Document</code>.</p>
 
   <!-- next two paragraphs are nearly identical to the navigate-html
   section and similar to the "navigate-ua-inline" section, and the
@@ -42295,8 +42291,8 @@
 
   <p>Upon creation of the <code>Document</code> object, the user agent
   must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache
-  selection algorithm</a> with the <var title="">document-is-markup</var> flag set to false, no manifest,
-  and passing in the newly-created <code>Document</code>.</p>
+  selection algorithm</a> with no manifest, and passing in the
+  newly-created <code>Document</code>.</p>
 
   <p>After creating the <code>Document</code> object, but potentially
   before the page has finished fully loading, the user agent must
@@ -42328,8 +42324,8 @@
 
   <p>Upon creation of the <code>Document</code> object, the user agent
   must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache
-  selection algorithm</a> with the <var title="">document-is-markup</var> flag set to false, no manifest,
-  and passing in the newly-created <code>Document</code>.</p>
+  selection algorithm</a> with no manifest, and passing in the
+  newly-created <code>Document</code>.</p>
 
   <p>After creating the <code>Document</code> object, but potentially
   before the page has finished fully loading, the user agent must
@@ -42364,8 +42360,8 @@
 
   <p>Upon creation of the <code>Document</code> object, the user agent
   must run the <a href=#concept-appcache-init title=concept-appcache-init>application cache
-  selection algorithm</a> with the <var title="">document-is-markup</var> flag set to false, no manifest,
-  passing in the newly-created <code>Document</code>.</p>
+  selection algorithm</a> with no manifest, passing in the
+  newly-created <code>Document</code>.</p>
 
   <p>After creating the <code>Document</code> object, but potentially
   before the page has been completely set up, the user agent must
@@ -54246,7 +54242,7 @@
     otherwise, if there is no such attribute or resolving it fails,
     run the <a href=#concept-appcache-init title=concept-appcache-init>application cache
     selection algorithm</a> with no manifest. The algorithm must be
-    passed the <code>Document</code> object, and the <var title="">document-is-markup</var> flag must be set to true.</p>
+    passed the <code>Document</code> object.</p>
 
     <p>Switch the <a href=#insertion-mode>insertion mode</a> to "<a href=#the-before-head-insertion-mode title="insertion mode: before head">before head</a>".</p>
Received on Friday, 13 February 2009 02:38:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:58 GMT