- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 27 Jun 2008 04:17:45 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv27534
Modified Files:
Overview.html
Log Message:
URLify navigation and neighboring sections; fix validation errors (whatwg r1814)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1002
retrieving revision 1.1003
diff -u -d -r1.1002 -r1.1003
--- Overview.html 27 Jun 2008 02:08:52 -0000 1.1002
+++ Overview.html 27 Jun 2008 04:17:43 -0000 1.1003
@@ -32763,10 +32763,10 @@
"start of line".</p>
<!-- SECURITY -->
<p>If the resulting <a href="#absolute">absolute URL</a> for <var
- title="">part two has a different <a href="#ltschemegt"
+ title="">part two</var> has a different <a href="#ltschemegt"
title=url-scheme><scheme></a> component than the manifest's URL
(compared case-insensitively<!-- XXX ASCII -->), then jump back to the
- step labeled "start of line".</var></p>
+ step labeled "start of line".</p>
<p>Drop any the <a href="#ltfragmentgt"
title=url-fragment><fragment></a> components of the resulting <a
@@ -33541,12 +33541,13 @@
href="#length8">length</a></code>-1</span>.
<p>The <dfn id=itemindex4 title=dom-appcache-item><code>item(<var
- title="">index</var>)</code></dfn> method must return the absolute URL of
- the <a href="#dynamic3" title=concept-appcache-dynamic>dynamic entry</a>
- with index <var title="">index</var> from the <a
- href="#application0">application cache</a>, if one is associated with the
- <code><a href="#applicationcache">ApplicationCache</a></code> object. If
- the object is not associated with any application cache, or if the <var
+ title="">index</var>)</code></dfn> method must return the <a
+ href="#absolute">absolute URL</a> of the <a href="#dynamic3"
+ title=concept-appcache-dynamic>dynamic entry</a> with index <var
+ title="">index</var> from the <a href="#application0">application
+ cache</a>, if one is associated with the <code><a
+ href="#applicationcache">ApplicationCache</a></code> object. If the object
+ is not associated with any application cache, or if the <var
title="">index</var> argument is lower than zero or greater than
<span><code title=dom-appcache-length><a
href="#length8">length</a></code>-1</span>, the method must instead raise
@@ -34283,8 +34284,7 @@
<p>In addition, a user agent could ignore calls to <code
title=dom-history-pushState><a href="#pushstate">pushState()</a></code>
that are invoked on a timer, or from event handlers that do not represent
- a clear user action, or that are invoked in rapid succession.</p>
- <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXURL \(url\|uri\|iri\) -->
+ a clear user action, or that are invoked in rapid succession.
<h3 id=browsing0><span class=secno>5.9 </span>Browsing the Web</h3>
@@ -34373,27 +34373,27 @@
affect the browsing context, then abort these steps and proceed with
that mechanism instead.
- <li> <!-- XXXURL change to URL -->
+ <li>
<p>If the new resource is to be fetched using HTTP GET or equivalent, and
if the browsing context being navigated is a <a
href="#top-level">top-level browsing context</a>, then check if there
are any <a href="#application0" title="application cache">application
caches</a> that have a <a href="#the-manifest"
title=concept-appcache-manifest>manifest</a> with the <a
- href="#same-origin">same origin</a> as the URI in question, and that
- have this URI as one of their entries (excluding entries marked as <a
+ href="#same-origin">same origin</a> as the URL in question, and that
+ have this URL as one of their entries (excluding entries marked as <a
href="#foreign" title=concept-appcache-foreign>foreign</a>), and that
already contain their manifest, categorized as a <a href="#the-manifest"
title=concept-appcache-manifest>manifest</a>. If so, then the user agent
must then fetch the resource from the <a href="#select0"
title=concept-appcache-selection>most appropriate application cache</a>
of those that match.</p>
- <!-- XXXURL JSURI issue -->
+
<p>Otherwise, start fetching<!-- XXX xref --> the new resource in the
appropriate manner (e.g. performing an HTTP GET or POST operation, or
reading the file from disk, or executing script in the case of a <a
href="#the-javascript" title="javascript protocol"><code
- title="">javascript:</code> URI</a>). If this results in a redirect,
+ title="">javascript:</code> URL</a>). If this results in a redirect,
return to <a href=navigate-fragid-step>the step labeled "fragment
identifiers"</a> with the new resource.</p>
@@ -34414,10 +34414,10 @@
user agent may allow the user to cancel this navigation attempt or start
other navigation attempts.
- <li> <!-- XXXURL change to URL, "fetch"? -->
+ <li>
<p>If the resource was not fetched from an <a
href="#application0">application cache</a>, and was to be fetched using
- HTTP GET or equivalent, and its URI <a href="#matches"
+ HTTP GET or equivalent, and its URL <a href="#matches"
title=concept-appcache-matches-oppcache>matches the opportunistic
caching namespace</a> of one or more application caches, and the user
didn't cancel the navigation attempt during the previous step, then:</p>
@@ -34440,13 +34440,13 @@
title=concept-appcache-foreign>foreign</a>, then the user agent must
discard the failed load and instead continue along these steps using
<var title="">candidate</var> as the resource.</p>
- <!-- XXXURL change to URL -->
+
<p>For the purposes of session history (and features that depend on
- session history, e.g. bookmarking) the user agent must use the URI of
+ session history, e.g. bookmarking) the user agent must use the URL of
the resource that was requested (the one that matched the
opportunistic caching namespace), not the fallback resource. However,
the user agent may indicate to the user that the original page load
- failed, that the page used was a fallback resource, and what the URI
+ failed, that the page used was a fallback resource, and what the URL
of the fallback resource actually is.</p>
<dt>Otherwise
@@ -34664,26 +34664,26 @@
that must be used when determining the character encoding according to the
rules given in the above specifications. Once the character encoding is
established, the <a href="#character1">document's character encoding</a>
- must be set to that character encoding.</p>
- <!-- XXXURL change to URL, (algorithms?) -->
+ must be set to that character encoding.
<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-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"
+ inserted into the DOM, the user agent must <a href="#resolve"
+ title="resolve a url">resolve</a> the value of that attribute, and if that
+ is successful, must run the <a href="#application2"
title=concept-appcache-init-with-attribute>application cache selection
- algorithm</a> with the value of that attribute, resolved relative to the
- <span>element's base URI</span>, as the manifest URI. Otherwise, as soon
- as the root element is inserted into the DOM, the user agent must run the
- <a href="#application3"
+ algorithm</a> with the resulting <a href="#absolute">absolute URL</a> as
+ the manifest URL. Otherwise, if the attribute is absent or resolving it
+ fails, then as soon as the root element is inserted into the DOM, the user
+ agent must run the <a href="#application3"
title=concept-appcache-init-no-attribute>application cache selection
- algorithm</a> with no manifest.</p>
- <!-- XXXURL change to URL -->
+ algorithm</a> with no manifest.
<p class=note>Because the processing of the <code
title=attr-html-manifest><a href="#manifest">manifest</a></code> attribute
- happens only once the root element is parsed, any URIs referenced by
+ happens only once the root element is parsed, any URLs 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
@@ -34861,12 +34861,12 @@
<h4 id=scroll-to-fragid><span class=secno>5.9.8 </span><dfn id=navigating0
title=navigate-fragid>Navigating to a fragment identifier</dfn></h4>
- <!-- XXXURL change to URL; XXXDOCURL? -->
<p>When a user agent is supposed to navigate to a fragment identifier, then
the user agent must <a href="#update2">update the session history with the
new page</a>, where "the new page" has the same <code>Document</code> as
- before but with the URI having the newly specified fragment identifier.
+ before but with the URL having the newly specified fragment identifier.</p>
+ <!-- XXXDOCURL ? -->
<p>Part of that algorithm involves the user agent having to <a
href="#scroll">scroll to the fragment identifier</a>, which is the
@@ -34889,14 +34889,15 @@
following processing model must be followed to determine what <a
href="#the-indicated">the indicated part of the document</a> is.
- <ol><!-- XXXURL algorithms -->
-
+ <ol>
<li>
- <p>Let <i>fragid</i> be the <fragment> part of the URI. <a
- href="#references">[RFC3987]</a>
+ <p><a href="#parse0" title="parse a url">Parse</a> the <a
+ href="#url">URL</a>, and let <i>fragid</i> be the <a
+ href="#ltfragmentgt" title=url-fragment><fragment></a> component
+ of the URL.
</li>
- <!-- IRI,
- ifragment? XXXURL (refer to parsing defined in this spec) -->
+ <!-- parsing can't fail, since we checked earlier on
+ when navigating -->
<li>
<p>If <i>fragid</i> is the empty string, then the indicated part of the
@@ -35032,16 +35033,14 @@
<p>If the <i>specified entry</i> is a state object or the first entry for
a <code>Document</code>, the user agent must <a href="#activating0"
title="activate the state object">activate that entry</a>.
- </li>
- <!-- XXXURL change to URL -->
<li>
- <p>If the <i>specified entry</i> has a URI that differs from the <a
+ <p>If the <i>specified entry</i> has a URL that differs from the <a
href="#current1">current entry</a>'s only by its fragment identifier,
and the two share the same <code>Document</code> object, then <a
href="#firing2">fire a simple event</a> with the name
<code>hashchanged</code> at <a href="#the-body1">the <code>body</code>
- element</a>, and, if the new URI has a fragment identifier, <a
+ element</a>, and, if the new URL has a fragment identifier, <a
href="#scroll">scroll to the fragment identifier</a>.
<li>
@@ -36153,12 +36152,11 @@
this information to the third party along with any identifying information
(names, credit card numbers, addresses) obtained by the site. If a third
party cooperates with multiple sites to obtain such information, a profile
- can still be created.</p>
- <!-- XXXURL change to URL -->
+ can still be created.
<p>However, user tracking is to some extent possible even with no
cooperation from the user agent whatsoever, for instance by using session
- identifiers in URIs, a technique already commonly used for innocuous
+ identifiers in URLs, a technique already commonly used for innocuous
purposes but easily repurposed for user tracking (even retroactively).
This information can then be shared with other sites, using using
visitors' IP addresses and other user-specific data (e.g. user-agent
@@ -36241,7 +36239,8 @@
title="">?</code> placeholder feature of the <code
title=dom-sqltransaction-executeSql><a
href="#executesql">executeSql()</a></code> method, and to never construct
- SQL statements on the fly.
+ SQL statements on the fly.</p>
+ <!-- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXURL \(url\|uri\|iri\) -->
<h3 id=links><span class=secno>5.11 </span>Links</h3>
Received on Friday, 27 June 2008 04:18:25 UTC