[html5] r4763 - [e] (0) internal editor's notes about url parsing

[whatwg at whatwg.org]

Author: ianh
Date: 2010-02-17 13:57:27 -0800 (Wed, 17 Feb 2010)
New Revision: 4763

Modified:
   complete.html
   index
   source
Log:
[e] (0) internal editor's notes about url parsing

Modified: complete.html
===================================================================
--- complete.html	2010-02-17 21:30:00 UTC (rev 4762)
+++ complete.html	2010-02-17 21:57:27 UTC (rev 4763)
@@ -20659,6 +20659,10 @@
 
    <li>
 
+    <!-- if we get to this point we know we can successfully parsed
+    the URL, since this algorithm is only used after fetching the
+    resource in the steps above -->
+
     <p>Otherwise, if the <a href=#url-path title=url-path><path></a>
     component of the <a href=#url>URL</a> of the specified resource (after
     any redirects) matches a pattern that a <a href=#plugin>plugin</a>
@@ -21046,6 +21050,10 @@
 
        <li>
 
+        <!-- if we get to this point we know we can successfully
+        parsed the URL, since this algorithm is only used after
+        fetching the resource in the steps above -->
+
         <p>If the <var title="">resource type</var> is still unknown
         at this point, but the <a href=#url-path title=url-path><path></a> component of the
         <a href=#url>URL</a> of the specified resource (after any
@@ -40605,6 +40613,9 @@
       <var title="">form data set</var> using the <a href=#application/x-www-form-urlencoded-encoding-algorithm><code title="">application/x-www-form-urlencoded</code> encoding
       algorithm</a>, interpreted as a US-ASCII string.</p>
 
+      <!-- by this point we've already tried to resolve the URL, so we
+      know we can parse it -->
+
       <p>Let <var title="">destination</var> be a new <a href=#url>URL</a>
       that is equal to the <var title="">action</var> except that its
       <a href=#url-query title=url-query><query></a> component is

Modified: index
===================================================================
--- index	2010-02-17 21:30:00 UTC (rev 4762)
+++ index	2010-02-17 21:57:27 UTC (rev 4763)
@@ -20561,6 +20561,10 @@
 
    <li>
 
+    <!-- if we get to this point we know we can successfully parsed
+    the URL, since this algorithm is only used after fetching the
+    resource in the steps above -->
+
     <p>Otherwise, if the <a href=#url-path title=url-path><path></a>
     component of the <a href=#url>URL</a> of the specified resource (after
     any redirects) matches a pattern that a <a href=#plugin>plugin</a>
@@ -20948,6 +20952,10 @@
 
        <li>
 
+        <!-- if we get to this point we know we can successfully
+        parsed the URL, since this algorithm is only used after
+        fetching the resource in the steps above -->
+
         <p>If the <var title="">resource type</var> is still unknown
         at this point, but the <a href=#url-path title=url-path><path></a> component of the
         <a href=#url>URL</a> of the specified resource (after any
@@ -40507,6 +40515,9 @@
       <var title="">form data set</var> using the <a href=#application/x-www-form-urlencoded-encoding-algorithm><code title="">application/x-www-form-urlencoded</code> encoding
       algorithm</a>, interpreted as a US-ASCII string.</p>
 
+      <!-- by this point we've already tried to resolve the URL, so we
+      know we can parse it -->
+
       <p>Let <var title="">destination</var> be a new <a href=#url>URL</a>
       that is equal to the <var title="">action</var> except that its
       <a href=#url-query title=url-query><query></a> component is

Modified: source
===================================================================
--- source	2010-02-17 21:30:00 UTC (rev 4762)
+++ source	2010-02-17 21:57:27 UTC (rev 4763)
@@ -22016,6 +22016,10 @@
 
    <li>
 
+    <!-- if we get to this point we know we can successfully parsed
+    the URL, since this algorithm is only used after fetching the
+    resource in the steps above -->
+
     <p>Otherwise, if the <span title="url-path"><path></span>
     component of the <span>URL</span> of the specified resource (after
     any redirects) matches a pattern that a <span>plugin</span>
@@ -22438,6 +22442,10 @@
 
        <li>
 
+        <!-- if we get to this point we know we can successfully
+        parsed the URL, since this algorithm is only used after
+        fetching the resource in the steps above -->
+
         <p>If the <var title="">resource type</var> is still unknown
         at this point, but the <span
         title="url-path"><path></span> component of the
@@ -45332,6 +45340,9 @@
       title="">application/x-www-form-urlencoded</code> encoding
       algorithm</span>, interpreted as a US-ASCII string.</p>
 
+      <!-- by this point we've already tried to resolve the URL, so we
+      know we can parse it -->
+
       <p>Let <var title="">destination</var> be a new <span>URL</span>
       that is equal to the <var title="">action</var> except that its
       <span title="url-query"><query></span> component is