Skip to content

Commit

Permalink
[e] (0) fax: is apparently no longer in season.
Browse files Browse the repository at this point in the history
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8855

git-svn-id: http://svn.whatwg.org/webapps@4777 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Feb 18, 2010
1 parent 603fcbe commit b507eb9
Show file tree
Hide file tree
Showing 3 changed files with 62 additions and 47 deletions.
38 changes: 20 additions & 18 deletions complete.html
Expand Up @@ -59605,17 +59605,18 @@ <h4 id=custom-handlers><span class=secno>7.4.2 </span>Custom scheme and content

<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 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
for particular schemes. For example, an online telephone messaging
service could register itself as a handler of the <code>sms:</code>
scheme (<a href=#refsRFC5724>[RFC5724]</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
for content in a particular <a href=#mime-type>MIME type</a>. For example, the
same online fax service could register itself as a handler for
<code>image/g3fax</code> files (<a href=#refsRFC1494>[RFC1494]</a>), so that if the user has no
native application capable of handling G3 Facsimile byte streams,
his Web browser can instead suggest he use that site to view the
image.</p>
same online telephone messaging service could register itself as a
handler for <code>text/directory</code> files (<a href=#refsRFC2425>[RFC2425]</a>), so that if the user has no
native application capable of handling vCards (<a href=#refsRFC2426>[RFC2426]</a>), his Web browser can instead
suggest he use that site to view contact information stored on
vCards that he opens.</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="">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>
Expand Down Expand Up @@ -59659,7 +59660,7 @@ <h4 id=custom-handlers><span class=secno>7.4.2 </span>Custom scheme and content

<dd>

<p>A scheme, such as <code>ftp</code> or <code>fax</code>. The
<p>A scheme, such as <code>ftp</code> or <code>sms</code>. The
scheme must be compared in an <a href=#ascii-case-insensitive>ASCII case-insensitive</a>
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
Expand Down Expand Up @@ -88499,11 +88500,6 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der
Poel. IETF.</dd>

<dt id=refsRFC1494>[RFC1494]</dt>
<dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc1494.txt>Equivalences between
1988 X.400 and RFC-822 Message Bodies</a></cite>, H. Alvestrand,
S. Thompson. IETF.</dd>

<dt id=refsRFC1554>[RFC1554]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc1554.txt>ISO-2022-JP-2:
Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF.</dd>
Expand Down Expand Up @@ -88559,6 +88555,11 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2388.txt>Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>

<dt id=refsRFC2425>[RFC2425]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2425.txt>A MIME
Content-Type for Directory Information</a></cite>, T. Howes,
M. Smith, F. Dawson. IETF.</dd>

<dt id=refsRFC2426>[RFC2426]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2426.txt>vCard MIME Directory
Profile</a></cite>, F. Dawson, T. Howes. IETF.</dd>
Expand All @@ -88581,10 +88582,6 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2646.txt>The Text/Plain Format
Parameter</a></cite>, R. Gellens. IETF.</dd>

<dt id=refsRFC2806>[RFC2806]</dt>
<dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc2806.txt>URLs for Telephone
Calls</a></cite>, A. Vaha-Sipila. IETF.</dd>

<dt id=refsRFC3023>[RFC3023]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc3023.txt>XML Media
Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF.</dd>
Expand Down Expand Up @@ -88649,6 +88646,11 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
<dd><cite><a href=http://www.ietf.org/rfc/rfc5322.txt>Internet Message
Format</a></cite>, P. Resnick. IETF.</dd>

<dt id=refsRFC5724>[RFC5724]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc5724.txt>URI Scheme
for Global System for Mobile Communications (GSM) Short Message
Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>

<dt id=refsSCSU>[SCSU]</dt>
<dd>(Non-normative) <cite><a href=http://www.unicode.org/reports/tr6/>UTR #6: A Standard
Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
Expand Down
38 changes: 20 additions & 18 deletions index
Expand Up @@ -59527,17 +59527,18 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {

<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 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
for particular schemes. For example, an online telephone messaging
service could register itself as a handler of the <code>sms:</code>
scheme (<a href=#refsRFC5724>[RFC5724]</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
for content in a particular <a href=#mime-type>MIME type</a>. For example, the
same online fax service could register itself as a handler for
<code>image/g3fax</code> files (<a href=#refsRFC1494>[RFC1494]</a>), so that if the user has no
native application capable of handling G3 Facsimile byte streams,
his Web browser can instead suggest he use that site to view the
image.</p>
same online telephone messaging service could register itself as a
handler for <code>text/directory</code> files (<a href=#refsRFC2425>[RFC2425]</a>), so that if the user has no
native application capable of handling vCards (<a href=#refsRFC2426>[RFC2426]</a>), his Web browser can instead
suggest he use that site to view contact information stored on
vCards that he opens.</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="">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>
Expand Down Expand Up @@ -59581,7 +59582,7 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {

<dd>

<p>A scheme, such as <code>ftp</code> or <code>fax</code>. The
<p>A scheme, such as <code>ftp</code> or <code>sms</code>. The
scheme must be compared in an <a href=#ascii-case-insensitive>ASCII case-insensitive</a>
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
Expand Down Expand Up @@ -82957,11 +82958,6 @@ interface <a href=#htmldocument>HTMLDocument</a> {
Encoding for Internet Messages</a></cite>, J. Murai, M. Crispin, E. van der
Poel. IETF.</dd>

<dt id=refsRFC1494>[RFC1494]</dt>
<dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc1494.txt>Equivalences between
1988 X.400 and RFC-822 Message Bodies</a></cite>, H. Alvestrand,
S. Thompson. IETF.</dd>

<dt id=refsRFC1554>[RFC1554]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc1554.txt>ISO-2022-JP-2:
Multilingual Extension of ISO-2022-JP</a></cite>, M. Ohta, K. Handa. IETF.</dd>
Expand Down Expand Up @@ -83013,6 +83009,11 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<dd><cite><a href=http://www.ietf.org/rfc/rfc2388.txt>Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>

<dt id=refsRFC2425>[RFC2425]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2425.txt>A MIME
Content-Type for Directory Information</a></cite>, T. Howes,
M. Smith, F. Dawson. IETF.</dd>

<dt id=refsRFC2426>[RFC2426]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc2426.txt>vCard MIME Directory
Profile</a></cite>, F. Dawson, T. Howes. IETF.</dd>
Expand All @@ -83035,10 +83036,6 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<dd><cite><a href=http://www.ietf.org/rfc/rfc2646.txt>The Text/Plain Format
Parameter</a></cite>, R. Gellens. IETF.</dd>

<dt id=refsRFC2806>[RFC2806]</dt>
<dd>(Non-normative) <cite><a href=http://www.ietf.org/rfc/rfc2806.txt>URLs for Telephone
Calls</a></cite>, A. Vaha-Sipila. IETF.</dd>

<dt id=refsRFC3023>[RFC3023]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc3023.txt>XML Media
Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn. IETF.</dd>
Expand Down Expand Up @@ -83094,6 +83091,11 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<dd><cite><a href=http://www.ietf.org/rfc/rfc5322.txt>Internet Message
Format</a></cite>, P. Resnick. IETF.</dd>

<dt id=refsRFC5724>[RFC5724]</dt>
<dd><cite><a href=http://www.ietf.org/rfc/rfc5724.txt>URI Scheme
for Global System for Mobile Communications (GSM) Short Message
Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>

<dt id=refsSCSU>[SCSU]</dt>
<dd>(Non-normative) <cite><a href=http://www.unicode.org/reports/tr6/>UTR #6: A Standard
Compression Scheme For Unicode</a></cite>, M. Wolf, K. Whistler,
Expand Down
33 changes: 22 additions & 11 deletions source
Expand Up @@ -67360,20 +67360,21 @@ interface <dfn>NavigatorAbilities</dfn> {
<p>The <dfn
title="dom-navigator-registerProtocolHandler"><code>registerProtocolHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
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
for particular schemes. For example, an online telephone messaging
service could register itself as a handler of the <code>sms:</code>
scheme (<a href="#refsRFC5724">[RFC5724]</a>), so that if the user
clicks on such a link, he is given the opportunity to use that Web
site. Analogously, the <dfn
title="dom-navigator-registerContentHandler"><code>registerContentHandler()</code></dfn>
method allows Web sites to register themselves as possible handlers
for content in a particular <span>MIME type</span>. For example, the
same online fax service could register itself as a handler for
<code>image/g3fax</code> files (<a
href="#refsRFC1494">[RFC1494]</a>), so that if the user has no
native application capable of handling G3 Facsimile byte streams,
his Web browser can instead suggest he use that site to view the
image.</p>
same online telephone messaging service could register itself as a
handler for <code>text/directory</code> files (<a
href="#refsRFC2425">[RFC2425]</a>), so that if the user has no
native application capable of handling vCards (<a
href="#refsRFC2426">[RFC2426]</a>), his Web browser can instead
suggest he use that site to view contact information stored on
vCards that he opens.</p>

<dl class="domintro">

Expand Down Expand Up @@ -67424,7 +67425,7 @@ interface <dfn>NavigatorAbilities</dfn> {

<dd>

<p>A scheme, such as <code>ftp</code> or <code>fax</code>. The
<p>A scheme, such as <code>ftp</code> or <code>sms</code>. The
scheme must be compared in an <span>ASCII case-insensitive</span>
manner by user agents for the purposes of comparing with the
scheme part of URLs that they consider against the list of
Expand Down Expand Up @@ -99109,6 +99110,11 @@ interface <span>HTMLDocument</span> {
<dd><cite><a href="http://www.ietf.org/rfc/rfc2388.txt">Returning Values from
Forms: multipart/form-data</a></cite>, L. Masinter. IETF.</dd>

<dt id="refsRFC2425">[RFC2425]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2425.txt">A MIME
Content-Type for Directory Information</a></cite>, T. Howes,
M. Smith, F. Dawson. IETF.</dd>

<dt id="refsRFC2426">[RFC2426]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2426.txt">vCard MIME Directory
Profile</a></cite>, F. Dawson, T. Howes. IETF.</dd>
Expand Down Expand Up @@ -99202,6 +99208,11 @@ interface <span>HTMLDocument</span> {
<dd><cite><a href="http://www.ietf.org/rfc/rfc5322.txt">Internet Message
Format</a></cite>, P. Resnick. IETF.</dd>

<dt id="refsRFC5724">[RFC5724]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc5724.txt">URI Scheme
for Global System for Mobile Communications (GSM) Short Message
Service (SMS)</a></cite>, E. Wilde, A. Vaha-Sipila. IETF.</dd>

<dt id="refsSCSU">[SCSU]</dt>
<dd>(Non-normative) <cite><a
href="http://www.unicode.org/reports/tr6/">UTR #6: A Standard
Expand Down

0 comments on commit b507eb9

Please sign in to comment.