interfaces are replaceable https://www.w3.org/Bugs/Public/show_bug.cgi?id=15765
authorAnne van Kesteren <annevk@opera.com>
Mon, 14 May 2012 12:51:35 +0200
changeset 327f474a8a87d9
parent 31 f443226de0bd
child 33 b180c5dcbcfe
interfaces are replaceable https://www.w3.org/Bugs/Public/show_bug.cgi?id=15765
Overview.html
Overview.src.html
     1.1 --- a/Overview.html	Sat May 12 02:37:09 2012 +0900
     1.2 +++ b/Overview.html	Mon May 14 12:51:35 2012 +0200
     1.3 @@ -33,7 +33,7 @@
     1.4  
     1.5  <h1 class="head">URL</h1>
     1.6  
     1.7 -<h2 class="no-num no-toc" id="w3c-doctype">Living Draft &mdash; 11 May 2012</h2>
     1.8 +<h2 class="no-num no-toc" id="w3c-doctype">Living Draft &mdash; 14 May 2012</h2>
     1.9  
    1.10  <dl>
    1.11   <dt>This Version:</dt>
    1.12 @@ -56,7 +56,7 @@
    1.13  <p class="copyright"><a href="http://creativecommons.org/publicdomain/zero/1.0/" rel="license"><img alt="CC0" src="http://i.creativecommons.org/p/zero/1.0/80x15.png"></a>
    1.14  To the extent possible under law, the editors have waived all copyright and
    1.15  related or neighboring rights to this work. In addition, as of
    1.16 -11 May 2012, the editors have made this specification available
    1.17 +14 May 2012, the editors have made this specification available
    1.18  under the
    1.19  <a href="http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0" rel="license">Open Web Foundation Agreement Version 1.0</a>,
    1.20  which is available at
    1.21 @@ -134,7 +134,7 @@
    1.22  <li>defines various algorithms for dealing with URLs&mdash;in large part
    1.23  essentially by precisely documenting how current browsers deal with URLs
    1.24  <li>defines an API for constructing, parsing, and resolving URLs
    1.25 -<li>defines what a <a href="#url">URL</a> is, as well as what a
    1.26 +<li>defines what a <a href="#concept-url" title="concept-url">URL</a> is, as well as what a
    1.27  <a href="#valid-url">valid URL</a> is, along with various subtypes of valid URLs
    1.28  </ul>
    1.29  
    1.30 @@ -142,13 +142,13 @@
    1.31  <p><i>This section is non-normative.</i>
    1.32  <div class="XXX">
    1.33  <p>Browsers parse URLs differently depending on which operating
    1.34 -system they&rsquor;re running on. The problem is that they want to do sensible
    1.35 +system they&rsquo;re running on. The problem is that they want to do sensible
    1.36  things for file paths, but file paths look different on Windows and Unix
    1.37  systems.
    1.38  
    1.39  <p>How should we handle cases where browsers disagree with the
    1.40  regular expression in RFC 3986?  Currently, this document aims to describe
    1.41 -how browsers behave, but we&rsquor;ll likely need to compare that to RFC 3986 at
    1.42 +how browsers behave, but we&rsquo;ll likely need to compare that to RFC 3986 at
    1.43  some point.  Some specific differences that have been brought up on the
    1.44  mailing list:
    1.45  <ul>
    1.46 @@ -174,12 +174,12 @@
    1.47  
    1.48  <h2 id="terminology"><span class="secno">2 </span>Terminology</h2>
    1.49  
    1.50 -<p>A <dfn id="url">URL</dfn> is a string used to identify a resource.</p>
    1.51 +<p>A <dfn id="concept-url" title="concept-url">URL</dfn> is a string used to identify a resource.</p>
    1.52  
    1.53 -<p>A <dfn id="parsed-url">parsed URL</dfn> is a user-agent&rsquor;s in-memory representation
    1.54 +<p>A <dfn id="parsed-url">parsed URL</dfn> is a user-agent&rsquo;s in-memory representation
    1.55  stored as the result of <a href="#parse-a-url-0" title="parse a URL">parsing a URL</a>.
    1.56  
    1.57 -<p>A <a href="#url">URL</a> is an <dfn id="absolute-url">absolute URL</dfn> if <a href="#resolve-a-url-0" title="resolve a url">resolving</a> it results in the same output
    1.58 +<p>A <a href="#concept-url" title="concept-url">URL</a> is an <dfn id="absolute-url">absolute URL</dfn> if <a href="#resolve-a-url-0" title="resolve a url">resolving</a> it results in the same output
    1.59  regardless of what it is resolved relative to, and that output is
    1.60  not a failure.</p>
    1.61  
    1.62 @@ -193,22 +193,22 @@
    1.63  immediately after the <a href="#scheme">scheme</a>
    1.64  component and they are both U+002F SOLIDUS characters (//).</p>
    1.65  
    1.66 -<p>A <a href="#url">URL</a> is a <dfn id="valid-url">valid URL</dfn> if at least one of
    1.67 +<p>A <a href="#concept-url" title="concept-url">URL</a> is a <dfn id="valid-url">valid URL</dfn> if at least one of
    1.68  the following conditions holds:</p>
    1.69  
    1.70  <ul>
    1.71 - <li><p>The <a href="#url">URL</a> is a valid URI reference.
    1.72 + <li><p>The <a href="#concept-url" title="concept-url">URL</a> is a valid URI reference.
    1.73   <a href="#refsRFC3986">[RFC3986]</a>
    1.74  
    1.75 - <li><p>The <a href="#url">URL</a> is a valid IRI reference and it has no
    1.76 + <li><p>The <a href="#concept-url" title="concept-url">URL</a> is a valid IRI reference and it has no
    1.77   query component.
    1.78   <a href="#refsRFC3987">[RFC3987]</a>
    1.79  
    1.80 - <li><p>The <a href="#url">URL</a> is a valid IRI reference and its query
    1.81 + <li><p>The <a href="#concept-url" title="concept-url">URL</a> is a valid IRI reference and its query
    1.82   component contains no unescaped non-ASCII characters.
    1.83   <a href="#refsRFC3987">[RFC3987]</a>
    1.84  
    1.85 - <li><p>The <a href="#url">URL</a> is a valid IRI reference and the
    1.86 + <li><p>The <a href="#concept-url" title="concept-url">URL</a> is a valid IRI reference and the
    1.87   <a class="external" href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-document-encoding" title="concept-document-encoding">character encoding</a>
    1.88   of the URL's <code>Document</code> is UTF-8 or
    1.89   <a data-anolis-spec="html" href="#a-utf-16-encoding">a UTF-16 encoding</a>.
    1.90 @@ -251,7 +251,7 @@
    1.91  or equal to U+0020 (" ").
    1.92  
    1.93  <p>A <dfn id="slash-character">slash character</dfn> is either U+002F ("/") or U+005C ("\").
    1.94 -<p class="XXX">TODO: There&rsquor;s some question as to whether this is necessary
    1.95 +<p class="XXX">TODO: There&rsquo;s some question as to whether this is necessary
    1.96  for non-file URLs.
    1.97  
    1.98  <p>An <dfn id="authority-terminating-character">authority terminating character</dfn> is either a
    1.99 @@ -276,7 +276,7 @@
   1.100  <ol>
   1.101  <li>Consume all leading and trailing
   1.102  <a href="#control-character" title="control character">control characters</a>.
   1.103 -<p class="XXX">Don&rsquor;t we actually want to &ldquo;strip leading and trailing
   1.104 +<p class="XXX">Don&rsquo;t we actually want to &ldquo;strip leading and trailing
   1.105  whitespace&rdquo; here? (= removing &ldquo;space characters&rdquo; as defined in the
   1.106  Terminology section)
   1.107  <li><a href="#find-the-scheme-0">Find the scheme</a>.
   1.108 @@ -301,7 +301,7 @@
   1.109  solidus (slash character?), then the URL is a hierarchical URL.&rdquo; Related to
   1.110  that, would it be better to only use the term &ldquo;hierarchical URL&rdquo;
   1.111  consistently rather than talking about the scheme being hierarchical?
   1.112 -(After all, it really is the URL that&rsquor;s hierarchical, not the scheme...)
   1.113 +(After all, it really is the URL that&rsquo;s hierarchical, not the scheme...)
   1.114  <ol>
   1.115  <li>Determine the <dfn id="path">path</dfn> and remaining components as follows:
   1.116  <ul>
   1.117 @@ -436,16 +436,16 @@
   1.118  <a href="#resolved-url">resolved URL</a> is <var title="">relative-url</var>
   1.119  <a href="#resolve-a-string-as-a-relative-url-0" title="resolve a string as a relative URL">resolved as relative URL</a>;
   1.120  abort these steps.
   1.121 -<li>If <var title="">relative-url</var>&rsquor;s <a href="#scheme">scheme</a> contains any
   1.122 +<li>If <var title="">relative-url</var>&rsquo;s <a href="#scheme">scheme</a> contains any
   1.123  characters which are not &ldquo;valid scheme characters&rdquo;, the
   1.124  <a href="#resolved-url">resolved URL</a> is <var>relative-url</var>
   1.125  <a href="#resolve-a-string-as-a-relative-url-0" title="resolve a string as a relative URL">resolved as relative URL</a>;
   1.126  abort these steps.
   1.127  <p class="XXX">TODO: Define <i>valid scheme characters</i>
   1.128 -<li>If <var title="">base-url</var>&rsquor;s scheme is an
   1.129 +<li>If <var title="">base-url</var>&rsquo;s scheme is an
   1.130  <a href="#ascii-case-insensitive">ASCII case-insensitive</a> match
   1.131 -for <var title="">relative-url</var>&rsquor;s <a href="#scheme">scheme</a> and the shared scheme is
   1.132 -hierarchical, the <a href="#resolved-url">resolved URL</a> is <var>relative-url</var>&rsquor;s
   1.133 +for <var title="">relative-url</var>&rsquo;s <a href="#scheme">scheme</a> and the shared scheme is
   1.134 +hierarchical, the <a href="#resolved-url">resolved URL</a> is <var>relative-url</var>&rsquo;s
   1.135  <a href="#after-scheme">after-scheme</a>
   1.136  <a href="#resolve-a-string-as-a-relative-url-0" title="resolve a string as a relative URL">resolved as a relative URL</a>;
   1.137  abort these steps.
   1.138 @@ -460,8 +460,8 @@
   1.139  <a href="#parsed-url">parsed URL</a>
   1.140  <var title="">base-url</var>, determine the <a href="#resolved-url">resolved URL</a> as
   1.141  follows:
   1.142 -<p class="XXX">TODO: If base-url&rsquor;s scheme is not hierarchical, we can&rsquor;t
   1.143 -resolve as a relative URL.  We&rsquor;ll probably want to return an invalid URL.
   1.144 +<p class="XXX">TODO: If base-url&rsquo;s scheme is not hierarchical, we can&rsquo;t
   1.145 +resolve as a relative URL.  We&rsquo;ll probably want to return an invalid URL.
   1.146  Check what happens when resolving an empty string as a relative URL with a
   1.147  non-hierarchical base.
   1.148  <ol>
   1.149 @@ -501,7 +501,7 @@
   1.150  <a href="#parsed-url">parsed URL</a>
   1.151  <var title="">base-url</var>, let <var title="">resolved-url</var> be:
   1.152  <ul>
   1.153 -<li><var title="">base-url</var>&rsquor;s <a href="#scheme">scheme</a>
   1.154 +<li><var title="">base-url</var>&rsquo;s <a href="#scheme">scheme</a>
   1.155  <li>concatenated with ":",
   1.156  <li>concatenated with <var title="">relative-url</var>.
   1.157  </ul>
   1.158 @@ -517,9 +517,9 @@
   1.159  <a href="#parsed-url">parsed URL</a>
   1.160  <var title="">base-url</var>, let <var title="">resolved-url</var> be:
   1.161  <ul>
   1.162 -<li><var title="">base-url</var>&rsquor;s <a href="#scheme">scheme</a>
   1.163 +<li><var title="">base-url</var>&rsquo;s <a href="#scheme">scheme</a>
   1.164  <li>concatenated with "://",
   1.165 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#authority">authority</a>,
   1.166 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#authority">authority</a>,
   1.167  <li>concatenated with <var title="">relative-url</var>.
   1.168  </ul>
   1.169  The <a href="#resolved-url">resolved URL</a> is <var title="">resolved-url</var>
   1.170 @@ -535,13 +535,13 @@
   1.171  always has at least one &ldquo;/&rdquo; character?
   1.172  <ol>
   1.173  <li>Let the <var title="">directory-name</var> be the characters of the
   1.174 -<var title="">base-url</var>&rsquor;s path up to and including the last
   1.175 +<var title="">base-url</var>&rsquo;s path up to and including the last
   1.176   <a href="#slash-character">slash character</a>.
   1.177  <li>Let <var title="">resolved-url</var> be:
   1.178  <ul>
   1.179 -<li><var title="">base-url</var>&rsquor;s <a href="#scheme">scheme</a>
   1.180 +<li><var title="">base-url</var>&rsquo;s <a href="#scheme">scheme</a>
   1.181  <li>concatenated with "://",
   1.182 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#authority">authority</a>,
   1.183 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#authority">authority</a>,
   1.184  <li>concatenated with <var title="">directory name</var>,
   1.185  <li>concatenated with <var title="">relative-url</var>.
   1.186  </ul>
   1.187 @@ -557,10 +557,10 @@
   1.188  <a href="#parsed-url">parsed URL</a>
   1.189  <var title="">base-url</var>, let <var title="">resolved-url</var> be:
   1.190  <ul>
   1.191 -<li><var title="">base-url</var>&rsquor;s <a href="#scheme">scheme</a>
   1.192 +<li><var title="">base-url</var>&rsquo;s <a href="#scheme">scheme</a>
   1.193  <li>concatenated with "://",
   1.194 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#authority">authority</a>,
   1.195 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#path">path</a>,
   1.196 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#authority">authority</a>,
   1.197 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#path">path</a>,
   1.198  <li>concatenated with <var title="">relative-url</var>.
   1.199  </ul>
   1.200  The <a href="#resolved-url">resolved URL</a> is <var title="">resolved-url</var>
   1.201 @@ -575,12 +575,12 @@
   1.202  <a href="#parsed-url">parsed URL</a>
   1.203  <var title="">base-url</var>, let <var title="">resolved-url</var> be:
   1.204  <ul>
   1.205 -<li><var title="">base-url</var>&rsquor;s <a href="#scheme">scheme</a>
   1.206 +<li><var title="">base-url</var>&rsquo;s <a href="#scheme">scheme</a>
   1.207  <li>concatenated with "://",
   1.208 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#authority">authority</a>,
   1.209 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#path">path</a>,
   1.210 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#authority">authority</a>,
   1.211 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#path">path</a>,
   1.212  <li>concatenated with "?",
   1.213 -<li>concatenated with <var title="">base-url</var>&rsquor;s <a href="#query">query</a>,
   1.214 +<li>concatenated with <var title="">base-url</var>&rsquo;s <a href="#query">query</a>,
   1.215  <li>concatenated with <var title="">relative-url</var>.
   1.216  </ul>
   1.217  The <a href="#resolved-url">resolved URL</a> is <var title="">resolved-url</var>
   1.218 @@ -710,7 +710,7 @@
   1.219  <li>If the current character is "%", ...
   1.220  <p class="XXX">TODO: Handle percent-unescaping.
   1.221  <li>If the current character is one of U+0000-U+002A, U+002C, U+002F,
   1.222 -U+003B-U+0040, U+005C, U+005E, U+0060, or U+007B-U+007F, 
   1.223 +U+003B-U+0040, U+005C, U+005E, U+0060, or U+007B-U+007F,
   1.224  output the
   1.225  <span>utf8-percent-escaping</span> of the current character.
   1.226  <li>Otherwise, if the current character matches ALPHA, output the current
   1.227 @@ -732,10 +732,10 @@
   1.228  <ol>
   1.229  <li>Process each character of the path in sequence:
   1.230  <ul>
   1.231 -<li>If the current character is one of 
   1.232 +<li>If the current character is one of
   1.233  U+0000-U+0020, U+0022, U+0023, U+0025, U+003C, U+003E, U+003F, U+005C,
   1.234  U+005E, U+0060, U+007B-U+007D, or U+007F, or greater than or equal to
   1.235 -U+0080, 
   1.236 +U+0080,
   1.237  output the
   1.238  <span>utf8-percent-escaping</span> of the current character.
   1.239  <li>Otherwise, if the current character is ".": ...
   1.240 @@ -756,7 +756,7 @@
   1.241  <ul>
   1.242  <li>If the current character is among TODO, output the current character.
   1.243  <p class="XXX">TODO: which characters?
   1.244 -<li>Otherwise, 
   1.245 +<li>Otherwise,
   1.246  output the
   1.247  <span>utf8-percent-escaping</span> of the current character.
   1.248  <p class="XXX">TODO: We need to handle the goofy query escaping format.
   1.249 @@ -771,7 +771,7 @@
   1.250  <ul>
   1.251  <li>If the current character has a Unicode value greater than or equal to
   1.252  U+0020, output the current character.
   1.253 -<li>Otherwise, 
   1.254 +<li>Otherwise,
   1.255  output the
   1.256  <span>utf8-percent-escaping</span> of the current character.
   1.257  </ul>
   1.258 @@ -877,8 +877,8 @@
   1.259  
   1.260  <p>The <code><a href="#url">URL</a></code> object can be used by scripts to programmatically construct, parse, and resolve URLs.
   1.261  
   1.262 -<pre class="idl">[<a href="#dom-url" title="dom-URL">Constructor</a>(DOMString <var><a href="#url">url</a></var>, optional DOMString <var>baseURL</var>)]
   1.263 -interface [Replaceable] <dfn id="url-interface" title="URL interface">URL</dfn> {<!-- XXX [Replaceable] does not work for interfaces -->
   1.264 +<pre class="idl">[<a href="#dom-url" title="dom-URL">Constructor</a>(DOMString <var title="">url</var>, optional DOMString <var>baseURL</var>)]
   1.265 +interface <dfn id="url">URL</dfn> {
   1.266             attribute DOMString <a href="#dom-url-protocol" title="dom-url-protocol">protocol</a>;
   1.267             attribute DOMString <a href="#dom-url-username" title="dom-url-username">username</a>;
   1.268             attribute DOMString <a href="#dom-url-password" title="dom-url-password">password</a>;
   1.269 @@ -934,7 +934,7 @@
   1.270    and
   1.271    <a href="#dom-url-href" title="dom-url-href">href</a>
   1.272    attributes.
   1.273 -   
   1.274 +
   1.275    <dl class="domintro">
   1.276  
   1.277     <dt><var title="">url</var> . <code title="dom-url-protocol"><a href="#dom-url-protocol">protocol</a></code> [ = <var title="">value</var> ]</dt>
   1.278 @@ -1001,8 +1001,8 @@
   1.279    must act as described in this section.</p>
   1.280  
   1.281    <p>In addition, the
   1.282 -  <a href="#url-interface">URL interface</a>
   1.283 -  defines an <dfn id="concept-url-input" title="concept-url-input">input</dfn>, which is a <a href="#url">URL</a>
   1.284 +  <code><a href="#url">URL</a></code> interface
   1.285 +  defines an <dfn id="concept-url-input" title="concept-url-input">input</dfn>, which is a <a href="#concept-url" title="concept-url">URL</a>
   1.286    that the attributes act on, and a
   1.287    <dfn id="concept-url-setter" title="concept-url-setter">common setter action</dfn>,
   1.288    which is a set of steps invoked when any of the attributes' setters are
     2.1 --- a/Overview.src.html	Sat May 12 02:37:09 2012 +0900
     2.2 +++ b/Overview.src.html	Mon May 14 12:51:35 2012 +0200
     2.3 @@ -84,7 +84,7 @@
     2.4  <div class=publish>
     2.5  <h2 class="no-num no-toc">Abstract</h2>
     2.6  
     2.7 -<p>This specification defines the term <span>URL</span>, various algorithms
     2.8 +<p>This specification defines the term <span title=concept-url>URL</span>, various algorithms
     2.9  for dealing with URLs, and an API for constructing, parsing, and resolving
    2.10  URLs.
    2.11  
    2.12 @@ -143,7 +143,7 @@
    2.13  <li>defines various algorithms for dealing with URLs—in large part
    2.14  essentially by precisely documenting how current browsers deal with URLs
    2.15  <li>defines an API for constructing, parsing, and resolving URLs
    2.16 -<li>defines what a <span>URL</span> is, as well as what a
    2.17 +<li>defines what a <span title=concept-url>URL</span> is, as well as what a
    2.18  <span>valid URL</span> is, along with various subtypes of valid URLs
    2.19  </ul>
    2.20  
    2.21 @@ -183,12 +183,12 @@
    2.22  
    2.23  <h2>Terminology</h2>
    2.24  
    2.25 -<p>A <dfn>URL</dfn> is a string used to identify a resource.</p>
    2.26 +<p>A <dfn title=concept-url>URL</dfn> is a string used to identify a resource.</p>
    2.27  
    2.28  <p>A <dfn>parsed URL</dfn> is a user-agent’s in-memory representation
    2.29  stored as the result of <span title="parse a URL">parsing a URL</span>.
    2.30  
    2.31 -<p>A <span>URL</span> is an <dfn>absolute URL</dfn> if <span
    2.32 +<p>A <span title=concept-url>URL</span> is an <dfn>absolute URL</dfn> if <span
    2.33  title="resolve a url">resolving</span> it results in the same output
    2.34  regardless of what it is resolved relative to, and that output is
    2.35  not a failure.</p>
    2.36 @@ -205,22 +205,22 @@
    2.37  immediately after the <span>scheme</span>
    2.38  component and they are both U+002F SOLIDUS characters (//).</p>
    2.39  
    2.40 -<p>A <span>URL</span> is a <dfn>valid URL</dfn> if at least one of
    2.41 +<p>A <span title=concept-url>URL</span> is a <dfn>valid URL</dfn> if at least one of
    2.42  the following conditions holds:</p>
    2.43  
    2.44  <ul>
    2.45 - <li><p>The <span>URL</span> is a valid URI reference.
    2.46 + <li><p>The <span title=concept-url>URL</span> is a valid URI reference.
    2.47   <span data-anolis-ref>RFC3986</span>
    2.48  
    2.49 - <li><p>The <span>URL</span> is a valid IRI reference and it has no
    2.50 + <li><p>The <span title=concept-url>URL</span> is a valid IRI reference and it has no
    2.51   query component.
    2.52   <span data-anolis-ref>RFC3987</span>
    2.53  
    2.54 - <li><p>The <span>URL</span> is a valid IRI reference and its query
    2.55 + <li><p>The <span title=concept-url>URL</span> is a valid IRI reference and its query
    2.56   component contains no unescaped non-ASCII characters.
    2.57   <span data-anolis-ref>RFC3987</span>
    2.58  
    2.59 - <li><p>The <span>URL</span> is a valid IRI reference and the
    2.60 + <li><p>The <span title=concept-url>URL</span> is a valid IRI reference and the
    2.61   <span data-anolis-spec=dom title="concept-document-encoding">character encoding</span>
    2.62   of the URL's <code>Document</code> is UTF-8 or
    2.63   <span data-anolis-spec=html>a UTF-16 encoding</span>.
    2.64 @@ -722,7 +722,7 @@
    2.65  <li>If the current character is "%", ...
    2.66  <p class=XXX>TODO: Handle percent-unescaping.
    2.67  <li>If the current character is one of U+0000-U+002A, U+002C, U+002F,
    2.68 -U+003B-U+0040, U+005C, U+005E, U+0060, or U+007B-U+007F, 
    2.69 +U+003B-U+0040, U+005C, U+005E, U+0060, or U+007B-U+007F,
    2.70  output the
    2.71  <span>utf8-percent-escaping</span> of the current character.
    2.72  <li>Otherwise, if the current character matches ALPHA, output the current
    2.73 @@ -744,10 +744,10 @@
    2.74  <ol>
    2.75  <li>Process each character of the path in sequence:
    2.76  <ul>
    2.77 -<li>If the current character is one of 
    2.78 +<li>If the current character is one of
    2.79  U+0000-U+0020, U+0022, U+0023, U+0025, U+003C, U+003E, U+003F, U+005C,
    2.80  U+005E, U+0060, U+007B-U+007D, or U+007F, or greater than or equal to
    2.81 -U+0080, 
    2.82 +U+0080,
    2.83  output the
    2.84  <span>utf8-percent-escaping</span> of the current character.
    2.85  <li>Otherwise, if the current character is ".": ...
    2.86 @@ -768,7 +768,7 @@
    2.87  <ul>
    2.88  <li>If the current character is among TODO, output the current character.
    2.89  <p class=XXX>TODO: which characters?
    2.90 -<li>Otherwise, 
    2.91 +<li>Otherwise,
    2.92  output the
    2.93  <span>utf8-percent-escaping</span> of the current character.
    2.94  <p class=XXX>TODO: We need to handle the goofy query escaping format.
    2.95 @@ -783,7 +783,7 @@
    2.96  <ul>
    2.97  <li>If the current character has a Unicode value greater than or equal to
    2.98  U+0020, output the current character.
    2.99 -<li>Otherwise, 
   2.100 +<li>Otherwise,
   2.101  output the
   2.102  <span>utf8-percent-escaping</span> of the current character.
   2.103  </ul>
   2.104 @@ -889,8 +889,8 @@
   2.105  
   2.106  <p>The <code>URL</code> object can be used by scripts to programmatically construct, parse, and resolve URLs.
   2.107  
   2.108 -<pre class=idl>[<span title=dom-URL>Constructor</span>(DOMString <var>url</var>, optional DOMString <var>baseURL</var>)]
   2.109 -interface [Replaceable] <dfn title="URL interface">URL</dfn> {<!-- XXX [Replaceable] does not work for interfaces -->
   2.110 +<pre class=idl>[<span title=dom-URL>Constructor</span>(DOMString <var title>url</var>, optional DOMString <var>baseURL</var>)]
   2.111 +interface <dfn>URL</dfn> {
   2.112             attribute DOMString <span title=dom-url-protocol>protocol</span>;
   2.113             attribute DOMString <span title=dom-url-username>username</span>;
   2.114             attribute DOMString <span title=dom-url-password>password</span>;
   2.115 @@ -946,7 +946,7 @@
   2.116    and
   2.117    <span title="dom-url-href">href</span>
   2.118    attributes.
   2.119 -   
   2.120 +
   2.121    <dl class="domintro">
   2.122  
   2.123     <dt><var title="">url</var> . <code title="dom-url-protocol">protocol</code> [ = <var title="">value</var> ]</dt>
   2.124 @@ -1013,9 +1013,9 @@
   2.125    must act as described in this section.</p>
   2.126  
   2.127    <p>In addition, the
   2.128 -  <span>URL interface</span>
   2.129 +  <code>URL</code> interface
   2.130    defines an <dfn
   2.131 -  title="concept-url-input">input</dfn>, which is a <span>URL</span>
   2.132 +  title="concept-url-input">input</dfn>, which is a <span title=concept-url>URL</span>
   2.133    that the attributes act on, and a
   2.134    <dfn title="concept-url-setter">common setter action</dfn>,
   2.135    which is a set of steps invoked when any of the attributes' setters are