[html5] r1040 - /
whatwg at whatwg.org
whatwg at whatwg.org
Thu Oct 11 11:36:17 PDT 2007
Author: ianh
Date: 2007-10-11 11:36:16 -0700 (Thu, 11 Oct 2007)
New Revision: 1040
Modified:
index
source
Log:
[] (0) rename 'application' to 'manifest' and define it
Modified: index
===================================================================
--- index 2007-10-09 06:58:06 UTC (rev 1039)
+++ index 2007-10-11 18:36:16 UTC (rev 1040)
@@ -22,7 +22,7 @@
<h1 id=html-5>HTML 5</h1>
- <h2 class="no-num no-toc" id=working>Working Draft — 9 October 2007</h2>
+ <h2 class="no-num no-toc" id=working>Working Draft — 11 October 2007</h2>
<p>You can take part in this work. <a
href="http://www.whatwg.org/mailing-list">Join the working group's
@@ -6878,17 +6878,40 @@
<dt>Element-specific attributes:
- <dd>None (but see prose).
+ <dd><code title=attr-html-manifest><a href="#manifest">manifest</a></code></dd>
+ <!--<dd><code title="attr-html-xmlns">xmlns</code></dd>-->
<dt>DOM interface:
<dd>No difference from <code><a
- href="#htmlelement">HTMLElement</a></code>.
+ href="#htmlelement">HTMLElement</a></code>.</dd>
+ <!--
+ <dd>
+ <pre class="idl">interface <dfn>HTMLHtmlElement</dfn> : <span>HTMLElement</span> {
+};</pre>
+ </dd>
+-->
</dl>
<p>The <code><a href="#html">html</a></code> element represents the root of
an HTML document.
+ <p>The <dfn id=manifest
+ title=attr-html-manifest><code>manifest</code></dfn> attribute gives the
+ address of the document's <a href="#application0">application cache</a> <a
+ href="#the-manifest" title=concept-appcache-manifest>manifest</a>, if
+ there is one. If the attribute is present, the attribute's value must be a
+ valid URI (or IRI).
+
+ <p>The <code title=attr-html-manifest><a
+ href="#manifest">manifest</a></code> attribute only <a
+ href="#application2" title=concept-appcache-init-with-attribute>has an
+ effect</a> during the early stages of document load. Changing the
+ attribute dynamically thus has no effect (and thus, no DOM API is provided
+ for this attribute). Furthermore, as it is processed before any <code><a
+ href="#base">base</a></code> elements are seen, its value is not subject
+ to being made relative to any base URI.
+
<p>Though it has absolutely no effect and no meaning, the <code><a
href="#html">html</a></code> element, in <a href="#html-">HTML
documents</a>, may have an <code title="">xmlns</code> attribute
@@ -25904,15 +25927,16 @@
href="#top-level">top-level browsing context</a> was <a
href="#navigate" title=navigate>navigated</a> to that document and the
document indicated that this was its cache, using the <code
- title=attr-html-application>application</code> attribute.
+ title=attr-html-manifest><a href="#manifest">manifest</a></code>
+ attribute.
<dt><dfn id=the-manifest title=concept-appcache-manifest>The
manifest</dfn>
<dd>The resource corresponding to the URI that was given in an implicit
entry's <code><a href="#html">html</a></code> element's <code
- title=attr-html-application>application</code> attribute. The manifest
- is downloaded and processed during the <a
+ title=attr-html-manifest><a href="#manifest">manifest</a></code>
+ attribute. The manifest is downloaded and processed during the <a
href="#application1">application cache update process</a>. All the <a
href="#implicit" title=concept-appcache-implicit>implicit entries</a>
have the <a href="#same-schemehostport">same scheme/host/port</a> as
@@ -25925,8 +25949,9 @@
title=concept-appcache-manifest>manifest</a>. Explicit entries can also
be marked as <dfn id=foreign
title=concept-appcache-foreign>foreign</dfn>, which means that they
- have an <code title=attr-html-application>application</code> attribute
- but that it doesn't point at this cache's <a href="#the-manifest"
+ have an <code title=attr-html-manifest><a
+ href="#manifest">manifest</a></code> attribute but that it doesn't
+ point at this cache's <a href="#the-manifest"
title=concept-appcache-manifest>manifest</a>.
<dt><dfn id=fallback0 title=concept-appcache-fallback>Fallback
@@ -28080,9 +28105,9 @@
<p>If the root element, as parsed according to the XML specifications cited
above, is found to be an <code><a href="#html">html</a></code> element
- with an attribute <code title=attr-html-application>application</code>,
- then, as soon as the element is inserted into the DOM, the user agent must
- run the <a href="#application2"
+ with an attribute <code title=attr-html-manifest><a
+ href="#manifest">manifest</a></code>, then, as soon as the element is
+ inserted into the DOM, the user agent must run the <a href="#application2"
title=concept-appcache-init-with-attribute>application cache selection
algorithm</a> with the value of that attribute as the manifest URI.
Otherwise, as soon as the root element is inserted into the DOM, the user
@@ -28091,9 +28116,9 @@
algorithm</a> with no manifest.
<p class=note>Because the processing of the <code
- title=attr-html-application>application</code> attribute happens only once
- the root element is parsed, any URIs referenced by processing instructions
- before the root element (such as <code
+ title=attr-html-manifest><a href="#manifest">manifest</a></code> attribute
+ happens only once the root element is parsed, any URIs referenced by
+ processing instructions before the root element (such as <code
title=""><?xml-styleesheet?></code> and <code
title=""><?xbl?></code> PIs) will be fetched from the network and
cannot be cached.</p>
Modified: source
===================================================================
--- source 2007-10-09 06:58:06 UTC (rev 1039)
+++ source 2007-10-11 18:36:16 UTC (rev 1040)
@@ -5436,14 +5436,36 @@
- http://www.glazman.org/weblog/dotclear/index.php?2005/05/27/1055-adam-2
-->
<dt>Element-specific attributes:</dt>
- <dd>None (but see prose).</dd>
+ <dd><code title="attr-html-manifest">manifest</code></dd>
+ <!--<dd><code title="attr-html-xmlns">xmlns</code></dd>-->
<dt>DOM interface:</dt>
<dd>No difference from <code>HTMLElement</code>.</dd>
+<!--
+ <dd>
+ <pre class="idl">interface <dfn>HTMLHtmlElement</dfn> : <span>HTMLElement</span> {
+};</pre>
+ </dd>
+-->
</dl>
<p>The <code>html</code> element represents the root of an HTML
document.</p>
+ <p>The <dfn title="attr-html-manifest"><code>manifest</code></dfn>
+ attribute gives the address of the document's <span>application
+ cache</span> <span
+ title="concept-appcache-manifest">manifest</span>, if there is
+ one. If the attribute is present, the attribute's value must be a
+ valid URI (or IRI).</p>
+
+ <p>The <code title="attr-html-manifest">manifest</code> attribute
+ only <span title="concept-appcache-init-with-attribute">has an
+ effect</span> during the early stages of document load. Changing the
+ attribute dynamically thus has no effect (and thus, no DOM API is
+ provided for this attribute). Furthermore, as it is processed before
+ any <code>base</code> elements are seen, its value is not subject to
+ being made relative to any base URI.</p>
+
<p>Though it has absolutely no effect and no meaning, the
<code>html</code> element, in <span>HTML documents</span>, may have
an <code title="">xmlns</code> attribute specified, if, and only if,
@@ -23518,14 +23540,14 @@
<span>top-level browsing context</span> was <span
title="navigate">navigated</span> to that document and the
document indicated that this was its cache, using the <code
- title="attr-html-application">application</code> attribute.
+ title="attr-html-manifest">manifest</code> attribute.
<dt><dfn title="concept-appcache-manifest">The manifest</dfn>
<dd>The resource corresponding to the URI that was given in an
implicit entry's <code>html</code> element's <code
- title="attr-html-application">application</code> attribute. The
+ title="attr-html-manifest">manifest</code> attribute. The
manifest is downloaded and processed during the <span>application
cache update process</span>. All the <span
title="concept-appcache-implicit">implicit entries</span> have
@@ -23538,7 +23560,7 @@
title="concept-appcache-manifest">manifest</span>. Explicit
entries can also be marked as <dfn
title="concept-appcache-foreign">foreign</dfn>, which means that they
- have an <code title="attr-html-application">application</code>
+ have an <code title="attr-html-manifest">manifest</code>
attribute but that it doesn't point at this cache's <span
title="concept-appcache-manifest">manifest</span>.
@@ -25739,7 +25761,7 @@
<p>If the root element, as parsed according to the XML
specifications cited above, is found to be an <code>html</code>
element with an attribute <code
- title="attr-html-application">application</code>, then, as soon as
+ title="attr-html-manifest">manifest</code>, then, as soon as
the element is inserted into the DOM, the user agent must run the
<span title="concept-appcache-init-with-attribute">application cache
selection algorithm</span> with the value of that attribute as the
@@ -25749,7 +25771,7 @@
selection algorithm</span> with no manifest.</p>
<p class="note">Because the processing of the <code
- title="attr-html-application">application</code> attribute happens
+ title="attr-html-manifest">manifest</code> attribute happens
only once the root element is parsed, any URIs referenced by
processing instructions before the root element (such as <code
title=""><?xml-styleesheet?></code> and <code
More information about the Commit-Watchers
mailing list