W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2008

html5/spec Overview.html,1.1509,1.1510

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 15 Oct 2008 23:44:48 +0000
To: public-html-commits@w3.org
Message-Id: <E1KqG2q-0004aD-Fg@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv17569

Modified Files:
	Overview.html 
Log Message:
Make the online whitelist a prefix match feature, not an exact match feature. (whatwg r2337)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1509
retrieving revision 1.1510
diff -u -d -r1.1509 -r1.1510
--- Overview.html	15 Oct 2008 21:14:39 -0000	1.1509
+++ Overview.html	15 Oct 2008 23:44:45 -0000	1.1510
@@ -149,7 +149,7 @@
      <li><a href=#features-defined-in-other-specifications><span class=secno>2.2.2 </span>Features defined in other specifications</a></li>
      <li><a href=#common-conformance-requirements-for-apis-exposed-to-javascript><span class=secno>2.2.3 </span>Common conformance requirements for APIs exposed to
   JavaScript</a></ol></li>
-   <li><a href=#case-sensitivity><span class=secno>2.3 </span>Case-sensitivity</a></li>
+   <li><a href=#case-sensitivity-and-string-comparison><span class=secno>2.3 </span>Case-sensitivity and string comparison</a></li>
    <li><a href=#common-microsyntaxes><span class=secno>2.4 </span>Common microsyntaxes</a>
     <ol>
      <li><a href=#common-parser-idioms><span class=secno>2.4.1 </span>Common parser idioms</a></li>
@@ -1539,7 +1539,7 @@
   a <code class=XXX>NOT_SUPPORTED_ERR</code> exception must be
   raised.</p><!-- XXX DOMB --><p>Unless otherwise specified, if a method is passed more arguments than
   is defined for that method in its IDL definition, the excess
-  arguments must be ignored.<h3 id=case-sensitivity><span class=secno>2.3 </span>Case-sensitivity</h3><p>This specification defines several comparison operators for
+  arguments must be ignored.<h3 id=case-sensitivity-and-string-comparison><span class=secno>2.3 </span>Case-sensitivity and string comparison</h3><p>This specification defines several comparison operators for
   strings.<p>Comparing two strings in a <dfn id=case-sensitive>case-sensitive</dfn> manner means
   comparing them exactly, codepoint for codepoint.<p>Comparing two strings in a <dfn id=ascii-case-insensitive>ASCII case-insensitive</dfn>
   manner means comparing them exactly, codepoint for codepoint, except
@@ -1557,7 +1557,10 @@
   lowercase</dfn> means replacing all characters in the range U+0041
   .. U+005A (i.e. LATIN CAPITAL LETTER A to LATIN CAPITAL LETTER Z)
   with the corresponding characters in the range U+0061 .. U+007A
-  (i.e. LATIN SMALL LETTER A to LATIN SMALL LETTER Z).<h3 id=common-microsyntaxes><span class=secno>2.4 </span>Common microsyntaxes</h3><p>There are various places in HTML that accept particular data
+  (i.e. LATIN SMALL LETTER A to LATIN SMALL LETTER Z).<p>A string <var title="">pattern</var> is a <dfn id=prefix-match>prefix match</dfn>
+  for a string <var title="">s</var> when <var title="">pattern</var>
+  is not longer than <var title="">s</var> and truncating <var title="">s</var> to <var title="">pattern</var>'s length leaves the
+  two strings as matches of each other.<h3 id=common-microsyntaxes><span class=secno>2.4 </span>Common microsyntaxes</h3><p>There are various places in HTML that accept particular data
   types, such as dates or numbers. This section describes what the
   conformance criteria for content in those formats is, and how to
   parse them.</p><!-- XXX need to define how to handle U+000A LINE FEED and U+000D
@@ -28221,23 +28224,27 @@
    mechanism or equivalent, then <a href=#fetch>fetch</a> the resource
    normally and abort these steps.</li>
 
-   <li><p>If the resource's URL, ignoring its fragment identifier if
-   any, is listed in the <a href=#application-cache>application cache</a>'s <a href=#concept-appcache-onlinewhitelist title=concept-appcache-onlinewhitelist>online whitelist</a>,
-   then <a href=#fetch>fetch</a> the resource normally and abort these
-   steps.</li>
-
    <li><p>If the resource's URL is <a href=#concept-appcache-implicit title=concept-appcache-implicit>an implicit entry</a>, <a href=#concept-appcache-manifest title=concept-appcache-manifest>the manifest</a>, <a href=#concept-appcache-explicit title=concept-appcache-explicit>an explicit entry</a>, <a href=#concept-appcache-fallback title=concept-appcache-fallback>a fallback entry</a>, <a href=#concept-appcache-oppcache title=concept-appcache-oppcache>an opportunistically cached
    entry</a>, or a <a href=#concept-appcache-dynamic title=concept-appcache-dynamic>dynamic
    entry</a> in the <a href=#application-cache>application cache</a>, then get the
    resource from the cache (instead of fetching it), and abort these
    steps.</li>
 
+   <li><p>If there is an entry in the <a href=#application-cache>application cache</a>'s
+   <a href=#concept-appcache-onlinewhitelist title=concept-appcache-onlinewhitelist>online
+   whitelist</a> that has the <a href=#same-origin>same origin</a> as the
+   resource's URL and that is a <a href=#prefix-match>prefix match</a> for the
+   resource's URL, then <a href=#fetch>fetch</a> the resource normally and
+   abort these steps.</li>
+
    <li>
 
     <p>If the resource's URL has the <a href=#same-origin>same origin</a> as the
-    manifest's URL, and the start of the resource's URL's <a href=#url-path title=url-path>&lt;path&gt;</a> component is exactly matched
-    by the &lt;path&gt; component of an <a href=#concept-appcache-oppcache-ns title=concept-appcache-oppcache-ns>opportunistic caching
-    namespace</a> in the <a href=#application-cache>application cache</a>, then:
+    manifest's URL, and there is an <a href=#concept-appcache-oppcache-ns title=concept-appcache-oppcache-ns>opportunistic caching
+    namespace</a> in the <a href=#application-cache>application cache</a> whose
+    &lt;path&gt; component is a <a href=#prefix-match>prefix match</a> for the
+    resource's URL's <a href=#url-path title=url-path>&lt;path&gt;</a>
+    component, then:
 
     <p><a href=#fetch>Fetch</a> the resource normally. If this results 4xx
     or 5xx status codes or equivalent, or if there were network errors
Received on Wednesday, 15 October 2008 23:45:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 October 2008 23:45:04 GMT