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

html5/spec Overview.html,1.1014,1.1015

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 29 Jun 2008 09:41:08 +0000
To: public-html-commits@w3.org
Message-Id: <E1KCtPA-000256-MD@lionel-hutz.w3.org>

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

Modified Files:
	Overview.html 
Log Message:
Bring URL decomposition DOM attributes more into line with IE. (whatwg r1826)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1014
retrieving revision 1.1015
diff -u -d -r1.1014 -r1.1015
--- Overview.html	28 Jun 2008 09:01:52 -0000	1.1014
+++ Overview.html	29 Jun 2008 09:41:05 -0000	1.1015
@@ -59,7 +59,7 @@
     for HTML and XHTML</h2>
 
    <h2 class="no-num no-toc" id=editors0><!-- "W3C Working Draft" -->
-    Editor's Draft <!--ZZZ-->28 June 2008</h2>
+    Editor's Draft <!--ZZZ-->29 June 2008</h2>
 
    <dl><!-- ZZZ: update the month/day
     <dt>This Version:</dt>
@@ -207,7 +207,7 @@
 
   <p>The W3C <a href="http://www.w3.org/html/wg/">HTML Working Group</a> is
    the W3C working group responsible for this specification's progress along
-   the W3C Recommendation track. <!--ZZZ:--> This specification is the 28
+   the W3C Recommendation track. <!--ZZZ:--> This specification is the 29
    June 2008 <!--ZZZ "Working Draft"-->Editor's Draft. <!--:ZZZ--></p>
   <!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST -->
   <!-- relationship to other work (required) -->
@@ -3343,8 +3343,10 @@
 
      <td><a href="#ltportgt" title=url-port>&lt;port&gt;</a>
 
-     <td><a href="#input" title=concept-uda-input>input</a> is hierarchical
-      and uses a server-based naming authority
+     <td><a href="#input" title=concept-uda-input>input</a> is hierarchical,
+      uses a server-based naming authority, and contained a <a
+      href="#ltportgt" title=url-port>&lt;port&gt;</a> component (possibly an
+      empty one)
 
      <td>&mdash;
 
@@ -3378,7 +3380,9 @@
 
      <td><a href="#ltquerygt" title=url-query>&lt;query&gt;</a>
 
-     <td><a href="#input" title=concept-uda-input>input</a> is hierarchical
+     <td><a href="#input" title=concept-uda-input>input</a> is hierarchical,
+      and contained a <a href="#ltquerygt" title=url-query>&lt;query&gt;</a>
+      component (possibly an empty one)
 
      <td>U+003F QUESTION MARK ("<code title="">?</code>")
 
@@ -3394,7 +3398,9 @@
 
      <td><a href="#ltfragmentgt" title=url-fragment>&lt;fragment&gt;</a>
 
-     <td>Fragment identifier is longer than zero characters
+     <td><a href="#input" title=concept-uda-input>input</a> contained a <a
+      href="#ltfragmentgt" title=url-fragment>&lt;fragment&gt;</a> component
+      (possibly an empty one)
 
      <td>U+0023 NUMBER SIGN ("<code title="">#</code>")
 
@@ -3411,6 +3417,58 @@
   http://wp.netscape.com/eng/mozilla/3.0/handbook/javascript/ref_h-l.htm#84722
 -->
 
+  <div class=example>
+   <p>The table below demonstrates how the getter condition for <code
+    title=dom-uda-search><a href="#search">search</a></code> results in
+    different results depending on the exact original syntax of the URL:</p>
+
+   <table>
+    <thead>
+     <tr>
+      <th> Input URL
+
+      <th> <code title=dom-uda-search><a href="#search">search</a></code>
+       value
+
+      <th> Explanation
+
+    <tbody>
+     <tr>
+      <td> <code title="">http://example.com/</code>
+
+      <td> <i>empty string</i>
+
+      <td> No <a href="#ltquerygt" title=url-query>&lt;query&gt;</a>
+       component in input URL.
+
+     <tr>
+      <td> <code title="">http://example.com/?</code>
+
+      <td> <code title="">?</code>
+
+      <td> There is a <a href="#ltquerygt" title=url-query>&lt;query&gt;</a>
+       component, but it is empty. The question mark in the resulting value
+       is the prefix.
+
+     <tr>
+      <td> <code title="">http://example.com/?test</code>
+
+      <td> <code title="">?test</code>
+
+      <td> The <a href="#ltquerygt" title=url-query>&lt;query&gt;</a>
+       component has the value "<code title="">test</code>".
+
+     <tr>
+      <td> <code title="">http://example.com/?test#</code>
+
+      <td> <code title="">?test</code>
+
+      <td> The (empty) <a href="#ltfragmentgt"
+       title=url-fragment>&lt;fragment&gt;</a> component is not part of the
+       <a href="#ltquerygt" title=url-query>&lt;query&gt;</a> component.
+   </table>
+  </div>
+
   <h3 id=common0><span class=secno>2.4 </span>Common microsyntaxes</h3>
 
   <p>There are various places in HTML that accept particular data types, such
@@ -34483,7 +34541,7 @@
      reading the file from disk, or executing script in the case of a <a
      href="#the-javascript" title="javascript protocol"><code
      title="">javascript:</code> URL</a>). If this results in a redirect,
-     return to <a href=navigate-fragid-step>the step labeled "fragment
+     return to <a href="#navigate-fragid-step">the step labeled "fragment
      identifiers"</a> with the new resource.</p>
 
     <p class=example>For example, imagine an HTML page with an associated
@@ -34967,9 +35025,9 @@
    indicated part of the document</a> is brought to the user's attention. If
    there is no indicated part, then the user agent must not scroll anywhere.
 
-  <p>The <dfn id=the-indicated>the indicated part of the document</dfn> is
-   the one that the fragment identifier, if any, identifies. The semantics of
-   the fragment identifier in terms of mapping it to a specific DOM Node is
+  <p><dfn id=the-indicated>The indicated part of the document</dfn> is the
+   one that the fragment identifier, if any, identifies. The semantics of the
+   fragment identifier in terms of mapping it to a specific DOM Node is
    defined by the MIME type specification of the document's MIME Type (for
    example, the processing of fragment identifiers for XML MIME types is the
    responsibility of RFC3023).
Received on Sunday, 29 June 2008 09:41:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:57 GMT