[html5] r3190 - [e] (0) Fix wording to refer to 'schemes' not 'protocols' where appropriate. (cr [...]

whatwg at whatwg.org whatwg at whatwg.org
Thu Jun 4 15:53:38 PDT 2009


Author: ianh
Date: 2009-06-04 15:53:35 -0700 (Thu, 04 Jun 2009)
New Revision: 3190

Modified:
   index
   source
Log:
[e] (0) Fix wording to refer to 'schemes' not 'protocols' where appropriate. (credit: rb)

Modified: index
===================================================================
--- index	2009-06-04 22:28:58 UTC (rev 3189)
+++ index	2009-06-04 22:53:35 UTC (rev 3190)
@@ -758,7 +758,7 @@
    <li><a href=#system-state-and-capabilities><span class=secno>6.8 </span>System state and capabilities</a>
     <ol>
      <li><a href=#client-identification><span class=secno>6.8.1 </span>Client identification</a></li>
-     <li><a href=#custom-handlers><span class=secno>6.8.2 </span>Custom protocol and content handlers</a>
+     <li><a href=#custom-handlers><span class=secno>6.8.2 </span>Custom scheme and content handlers</a>
       <ol>
        <li><a href=#security-and-privacy><span class=secno>6.8.2.1 </span>Security and privacy</a></li>
        <li><a href=#sample-handler-impl><span class=secno>6.8.2.2 </span>Sample user interface</a></ol></li>
@@ -48971,7 +48971,7 @@
 
 [NoInterfaceObject, ImplementedOn=<a href=#navigator>Navigator</a>] interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
   // content handler registration
-  void <a href=#dom-navigator-registerprotocolhandler title=dom-navigator-registerProtocolHandler>registerProtocolHandler</a>(in DOMString protocol, in DOMString url, in DOMString title);
+  void <a href=#dom-navigator-registerprotocolhandler title=dom-navigator-registerProtocolHandler>registerProtocolHandler</a>(in DOMString scheme, in DOMString url, in DOMString title);
   void <a href=#dom-navigator-registercontenthandler title=dom-navigator-registerContentHandler>registerContentHandler</a>(in DOMString mimeType, in DOMString url, in DOMString title);
   void <a href=#dom-navigator-getstorageupdates title=dom-navigator-getStorageUpdates>getStorageUpdates</a>();
 <!--  XXX cookieEnabled geolocator javaEnabled mozIsLocallyAvailable preference
@@ -49072,12 +49072,12 @@
   </dl></div>
 
 
-  <h4 id=custom-handlers><span class=secno>6.8.2 </span>Custom protocol and content handlers</h4>
+  <h4 id=custom-handlers><span class=secno>6.8.2 </span>Custom scheme and content handlers</h4>
 
   <p>The <dfn id=dom-navigator-registerprotocolhandler title=dom-navigator-registerProtocolHandler><code>registerProtocolHandler()</code></dfn>
   method allows Web sites to register themselves as possible handlers
-  for particular protocols. For example, an online fax service could
-  register itself as a handler of the <code>fax:</code> protocol (<a href=#refsRFC2806>[RFC2806]</a>), so that if the user clicks on
+  for particular schemes. For example, an online fax service could
+  register itself as a handler of the <code>fax:</code> scheme (<a href=#refsRFC2806>[RFC2806]</a>), so that if the user clicks on
   such a link, he is given the opportunity to use that Web
   site. Analogously, the <dfn id=dom-navigator-registercontenthandler title=dom-navigator-registerContentHandler><code>registerContentHandler()</code></dfn>
   method allows Web sites to register themselves as possible handlers
@@ -49088,12 +49088,12 @@
   his Web browser can instead suggest he use that site to view the
   image.</p>
 
-  <dl class=domintro><dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerProtocolHandler><a href=#dom-navigator-registerprotocolhandler>registerProtocolHandler</a></code>(<var title="">protocol</var>, <var title="">url</var>, <var title="">title</var>)</dt>
+  <dl class=domintro><dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerProtocolHandler><a href=#dom-navigator-registerprotocolhandler>registerProtocolHandler</a></code>(<var title="">scheme</var>, <var title="">url</var>, <var title="">title</var>)</dt>
    <dt><var title="">window</var> . <code title=dom-navigator><a href=#dom-navigator>navigator</a></code> . <code title=dom-navigator-registerContentHandler><a href=#dom-navigator-registercontenthandler>registerContentHandler</a></code>(<var title="">mimeType</var>, <var title="">url</var>, <var title="">title</var>)</dt>
 
    <dd>
 
-    <p>Registers a handler for the given protocol or content type, at
+    <p>Registers a handler for the given scheme or content type, at
     the given URL, with the given title.</p>
 
     <p>The string "<code title="">%s</code>" in the URL is used as a
@@ -49136,7 +49136,7 @@
     scheme part of URLs that they consider against the list of
     registered handlers.</p>
 
-    <p>The <var title="">protocol</var> value, if it contains a colon
+    <p>The <var title="">scheme</var> value, if it contains a colon
     (as in "<code>ftp:</code>"), will never match anything, since
     schemes don't contain colons.</p>
 
@@ -49230,7 +49230,7 @@
    </dd>
 
   </dl><p>User agents should raise <code><a href=#security_err>SECURITY_ERR</a></code> exceptions if
-  the methods are called with <var title="">protocol</var> or <var title="">mimeType</var> values that the UA deems to be
+  the methods are called with <var title="">scheme</var> or <var title="">mimeType</var> values that the UA deems to be
   "privileged". For example, a site attempting to register a handler
   for <code>http</code> URLs or <code>text/html</code> content in a
   Web browser would likely cause an exception to be raised.</p>
@@ -49269,7 +49269,7 @@
   particular privacy concerns.</p>
 
   <p><strong>Hijacking all Web usage.</strong> User agents should not
-  allow protocols that are key to its normal operation, such as
+  allow schemes that are key to its normal operation, such as
   <code>http</code> or <code>https</code>, to be rerouted through
   third-party sites. This would allow a user's activities to be
   trivially tracked, and would allow user information, even in secure
@@ -49325,7 +49325,7 @@
   which might tell the third party that Example Corporation is
   intending to merge with The Sample Company. Implementors might wish
   to consider allowing administrators to disable this feature for
-  certain subdomains, content types, or protocols.</p>
+  certain subdomains, content types, or schemes.</p>
 
   <p><strong>Leaking secure URLs.</strong> User agents should not send
   HTTPS URLs to third-party sites registered as content handlers, in
@@ -49354,7 +49354,7 @@
   <p>A simple implementation of this feature for a desktop Web browser
   might work as follows.</p>
 
-  <p>The <code title=dom-navigator-registerProtocolHandler><a href=#dom-navigator-registerprotocolhandler>registerProtocolHandler()</a></code>
+  <p>The <code title=dom-navigator-registerContentHandler><a href=#dom-navigator-registercontenthandler>registerContentHandler()</a></code>
   method could display a modal dialog box:</p>
 
   <pre>||[ Content Handler Registration ]||||||||||||||||||||||||||||
@@ -49413,7 +49413,7 @@
 |      application at "kittens.example.org".                 |
 |                                                            |
 |  [ ] Always do this for resources using the "application/  |
-|      x-meowmeow" protocol in future.                       |
+|      x-meowmeow" type in future.                           |
 |                                                            |
 |                                     ( Ok )  (( Cancel ))   |
 |____________________________________________________________|</pre>
@@ -71075,6 +71075,7 @@
   Robert Blaut,
   Robert O'Callahan,
   Robert Sayre,
+  Robin Berjon,
   Roman Ivanov,
   Ryan King,
   S. Mike Dierken,

Modified: source
===================================================================
--- source	2009-06-04 22:28:58 UTC (rev 3189)
+++ source	2009-06-04 22:53:35 UTC (rev 3190)
@@ -55866,7 +55866,7 @@
 
 [NoInterfaceObject, ImplementedOn=<span>Navigator</span>] interface <dfn>NavigatorAbilities</dfn> {
   // content handler registration
-  void <span title="dom-navigator-registerProtocolHandler">registerProtocolHandler</span>(in DOMString protocol, in DOMString url, in DOMString title);
+  void <span title="dom-navigator-registerProtocolHandler">registerProtocolHandler</span>(in DOMString scheme, in DOMString url, in DOMString title);
   void <span title="dom-navigator-registerContentHandler">registerContentHandler</span>(in DOMString mimeType, in DOMString url, in DOMString title);
   void <span title="dom-navigator-getStorageUpdates">getStorageUpdates</span>();
 <!--  XXX cookieEnabled geolocator javaEnabled mozIsLocallyAvailable preference
@@ -55979,13 +55979,13 @@
   </div>
 
 
-  <h4 id="custom-handlers">Custom protocol and content handlers</h4>
+  <h4 id="custom-handlers">Custom scheme and content handlers</h4>
 
   <p>The <dfn
   title="dom-navigator-registerProtocolHandler"><code>registerProtocolHandler()</code></dfn>
   method allows Web sites to register themselves as possible handlers
-  for particular protocols. For example, an online fax service could
-  register itself as a handler of the <code>fax:</code> protocol (<a
+  for particular schemes. For example, an online fax service could
+  register itself as a handler of the <code>fax:</code> scheme (<a
   href="#refsRFC2806">[RFC2806]</a>), so that if the user clicks on
   such a link, he is given the opportunity to use that Web
   site. Analogously, the <dfn
@@ -56001,12 +56001,12 @@
 
   <dl class="domintro">
 
-   <dt><var title="">window</var> . <code title="dom-navigator">navigator</code> . <code title="dom-navigator-registerProtocolHandler">registerProtocolHandler</code>(<var title="">protocol</var>, <var title="">url</var>, <var title="">title</var>)</dt>
+   <dt><var title="">window</var> . <code title="dom-navigator">navigator</code> . <code title="dom-navigator-registerProtocolHandler">registerProtocolHandler</code>(<var title="">scheme</var>, <var title="">url</var>, <var title="">title</var>)</dt>
    <dt><var title="">window</var> . <code title="dom-navigator">navigator</code> . <code title="dom-navigator-registerContentHandler">registerContentHandler</code>(<var title="">mimeType</var>, <var title="">url</var>, <var title="">title</var>)</dt>
 
    <dd>
 
-    <p>Registers a handler for the given protocol or content type, at
+    <p>Registers a handler for the given scheme or content type, at
     the given URL, with the given title.</p>
 
     <p>The string "<code title="">%s</code>" in the URL is used as a
@@ -56054,7 +56054,7 @@
     scheme part of URLs that they consider against the list of
     registered handlers.</p>
 
-    <p>The <var title="">protocol</var> value, if it contains a colon
+    <p>The <var title="">scheme</var> value, if it contains a colon
     (as in "<code>ftp:</code>"), will never match anything, since
     schemes don't contain colons.</p>
 
@@ -56156,7 +56156,7 @@
   </dl>
 
   <p>User agents should raise <code>SECURITY_ERR</code> exceptions if
-  the methods are called with <var title="">protocol</var> or <var
+  the methods are called with <var title="">scheme</var> or <var
   title="">mimeType</var> values that the UA deems to be
   "privileged". For example, a site attempting to register a handler
   for <code>http</code> URLs or <code>text/html</code> content in a
@@ -56200,7 +56200,7 @@
   particular privacy concerns.</p>
 
   <p><strong>Hijacking all Web usage.</strong> User agents should not
-  allow protocols that are key to its normal operation, such as
+  allow schemes that are key to its normal operation, such as
   <code>http</code> or <code>https</code>, to be rerouted through
   third-party sites. This would allow a user's activities to be
   trivially tracked, and would allow user information, even in secure
@@ -56260,7 +56260,7 @@
   which might tell the third party that Example Corporation is
   intending to merge with The Sample Company. Implementors might wish
   to consider allowing administrators to disable this feature for
-  certain subdomains, content types, or protocols.</p>
+  certain subdomains, content types, or schemes.</p>
 
   <p><strong>Leaking secure URLs.</strong> User agents should not send
   HTTPS URLs to third-party sites registered as content handlers, in
@@ -56291,7 +56291,7 @@
   might work as follows.</p>
 
   <p>The <code
-  title="dom-navigator-registerProtocolHandler">registerProtocolHandler()</code>
+  title="dom-navigator-registerContentHandler">registerContentHandler()</code>
   method could display a modal dialog box:</p>
 
   <pre>||[ Content Handler Registration ]||||||||||||||||||||||||||||
@@ -56352,7 +56352,7 @@
 |      application at "kittens.example.org".                 |
 |                                                            |
 |  [ ] Always do this for resources using the "application/  |
-|      x-meowmeow" protocol in future.                       |
+|      x-meowmeow" type in future.                           |
 |                                                            |
 |                                     ( Ok )  (( Cancel ))   |
 |____________________________________________________________|</pre>
@@ -83760,6 +83760,7 @@
   Robert Blaut,
   Robert O'Callahan,
   Robert Sayre,
+  Robin Berjon,
   Roman Ivanov,
   Ryan King,
   S. Mike Dierken,




More information about the Commit-Watchers mailing list