Skip to content

Commit

Permalink
[e] (0) Fix wording to refer to 'schemes' not 'protocols' where appro…
Browse files Browse the repository at this point in the history 
…priate. (credit: rb)

git-svn-id: http://svn.whatwg.org/webapps@3190 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Jun 4, 2009
1 parent ac258e0 commit 40cdd52
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 25 deletions.
27 changes: 14 additions & 13 deletions index
View file
Expand Up @@ -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>
Expand Down Expand Up @@ -48971,7 +48971,7 @@ interface <dfn id=function>Function</dfn> {

[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
Expand Down Expand Up @@ -49072,12 +49072,12 @@ interface <dfn id=function>Function</dfn> {
</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
Expand All @@ -49088,12 +49088,12 @@ interface <dfn id=function>Function</dfn> {
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
Expand Down Expand Up @@ -49136,7 +49136,7 @@ interface <dfn id=function>Function</dfn> {
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>

Expand Down Expand Up @@ -49230,7 +49230,7 @@ interface <dfn id=function>Function</dfn> {
</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>
Expand Down Expand Up @@ -49269,7 +49269,7 @@ interface <dfn id=function>Function</dfn> {
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
Expand Down Expand Up @@ -49325,7 +49325,7 @@ interface <dfn id=function>Function</dfn> {
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
Expand Down Expand Up @@ -49354,7 +49354,7 @@ interface <dfn id=function>Function</dfn> {
<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 ]||||||||||||||||||||||||||||
Expand Down Expand Up @@ -49413,7 +49413,7 @@ interface <dfn id=function>Function</dfn> {
| 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>
Expand Down Expand Up @@ -71075,6 +71075,7 @@ S SPACER STRIKE TT U -->
Robert Blaut,
Robert O'Callahan,
Robert Sayre,
Robin Berjon,
Roman Ivanov,
Ryan King,
S. Mike Dierken,
Expand Down
25 changes: 13 additions & 12 deletions source
View file
Expand Up @@ -55866,7 +55866,7 @@ interface <dfn>Function</dfn> {

[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
Expand Down Expand Up @@ -55979,13 +55979,13 @@ interface <dfn>Function</dfn> {
</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
Expand All @@ -56001,12 +56001,12 @@ interface <dfn>Function</dfn> {

<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
Expand Down Expand Up @@ -56054,7 +56054,7 @@ interface <dfn>Function</dfn> {
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>

Expand Down Expand Up @@ -56156,7 +56156,7 @@ interface <dfn>Function</dfn> {
</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
Expand Down Expand Up @@ -56200,7 +56200,7 @@ interface <dfn>Function</dfn> {
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
Expand Down Expand Up @@ -56260,7 +56260,7 @@ interface <dfn>Function</dfn> {
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
Expand Down Expand Up @@ -56291,7 +56291,7 @@ interface <dfn>Function</dfn> {
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 ]||||||||||||||||||||||||||||
Expand Down Expand Up @@ -56352,7 +56352,7 @@ interface <dfn>Function</dfn> {
| 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>
Expand Down Expand Up @@ -83760,6 +83760,7 @@ S SPACER STRIKE TT U -->
Robert Blaut,
Robert O'Callahan,
Robert Sayre,
Robin Berjon,
Roman Ivanov,
Ryan King,
S. Mike Dierken,
Expand Down

0 comments on commit 40cdd52

Please sign in to comment.