Skip to content
Permalink
Browse files

[giow] (0) revert r5836 per http://lists.w3.org/Archives/Public/publi…

  • Loading branch information...
Hixie committed Mar 1, 2011
1 parent 05500b1 commit ab03111cfb8215aca5c0191e76ee2636760da7be
Showing with 78 additions and 5 deletions.
  1. +26 −2 complete.html
  2. +26 −2 index
  3. +26 −1 source

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 28 February 2011</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 1 March 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
not support, for example because it doesn't recognize the container
type, or it doesn't support the listed codecs.</p>

<p>The <a href=#mime-type>MIME type</a>
"<code>application/octet-stream</code>" with no parameters is never
<a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>. User
agents must treat that type as equivalent to the lack of any
explicit <a href=#content-type title=Content-Type>Content-Type metadata</a>
when it is used to label a potential <a href=#media-resource>media
resource</a>.</p>

<p class=note>In the absence of a <!-- pretty crazy -->
specification to the contrary, the <a href=#mime-type>MIME type</a>
"<code>application/octet-stream</code>" when used <em>with</em>
parameters, e.g.
"<code>application/octet-stream;codecs=theora</code>", <em>is</em>
<a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>,
since that parameter is not defined for that type.</p>

<dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>

<dd>

<p>The <dfn id=dom-navigator-canplaytype title=dom-navigator-canPlayType><code>canPlayType(<var title="">type</var>)</code></dfn> method must return the empty
string if <var title="">type</var> is <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user
agent knows it cannot render</a>; it must return "<code title="">probably</code>" if the user agent is confident that the
agent knows it cannot render</a> or is the type
"<code>application/octet-stream</code>"; it must return "<code title="">probably</code>" if the user agent is confident that the
type represents a <a href=#media-resource>media resource</a> that it can render if
used in with this <code><a href=#audio>audio</a></code> or <code><a href=#video>video</a></code> element;
and it must return "<code title="">maybe</code>" otherwise.
to network errors, causing the user agent to give up trying to
fetch the resource</dt>

<dt>If the <a href=#media-resource>media resource</a> is found to have <a href=#content-type title=Content-Type>Content-Type metadata</a> that, when
parsed as a <a href=#mime-type>MIME type</a> (including any codecs
described by the <code title="">codecs</code> parameter, if the
parameter is defined for that type), represents <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that
the user agent knows it cannot render</a> (even if the actual
<a href=#media-data>media data</a> is in a supported format)</dt>

<dt>If the <a href=#media-data>media data</a> can be fetched but is found by
inspection to be in an unsupported format, or can otherwise not
be rendered at all</dt>
28 index

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 28 February 2011</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 1 March 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
not support, for example because it doesn't recognize the container
type, or it doesn't support the listed codecs.</p>

<p>The <a href=#mime-type>MIME type</a>
"<code>application/octet-stream</code>" with no parameters is never
<a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>. User
agents must treat that type as equivalent to the lack of any
explicit <a href=#content-type title=Content-Type>Content-Type metadata</a>
when it is used to label a potential <a href=#media-resource>media
resource</a>.</p>

<p class=note>In the absence of a <!-- pretty crazy -->
specification to the contrary, the <a href=#mime-type>MIME type</a>
"<code>application/octet-stream</code>" when used <em>with</em>
parameters, e.g.
"<code>application/octet-stream;codecs=theora</code>", <em>is</em>
<a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user agent knows it cannot render</a>,
since that parameter is not defined for that type.</p>

<dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>

<dd>

<p>The <dfn id=dom-navigator-canplaytype title=dom-navigator-canPlayType><code>canPlayType(<var title="">type</var>)</code></dfn> method must return the empty
string if <var title="">type</var> is <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that the user
agent knows it cannot render</a>; it must return "<code title="">probably</code>" if the user agent is confident that the
agent knows it cannot render</a> or is the type
"<code>application/octet-stream</code>"; it must return "<code title="">probably</code>" if the user agent is confident that the
type represents a <a href=#media-resource>media resource</a> that it can render if
used in with this <code><a href=#audio>audio</a></code> or <code><a href=#video>video</a></code> element;
and it must return "<code title="">maybe</code>" otherwise.
to network errors, causing the user agent to give up trying to
fetch the resource</dt>

<dt>If the <a href=#media-resource>media resource</a> is found to have <a href=#content-type title=Content-Type>Content-Type metadata</a> that, when
parsed as a <a href=#mime-type>MIME type</a> (including any codecs
described by the <code title="">codecs</code> parameter, if the
parameter is defined for that type), represents <a href=#a-type-that-the-user-agent-knows-it-cannot-render>a type that
the user agent knows it cannot render</a> (even if the actual
<a href=#media-data>media data</a> is in a supported format)</dt>

<dt>If the <a href=#media-data>media data</a> can be fetched but is found by
inspection to be in an unsupported format, or can otherwise not
be rendered at all</dt>
27 source
not support, for example because it doesn't recognize the container
type, or it doesn't support the listed codecs.</p>

<p>The <span>MIME type</span>
"<code>application/octet-stream</code>" with no parameters is never
<span>a type that the user agent knows it cannot render</span>. User
agents must treat that type as equivalent to the lack of any
explicit <span title="Content-Type">Content-Type metadata</span>
when it is used to label a potential <span>media
resource</span>.</p>

<p class="note">In the absence of a <!-- pretty crazy -->
specification to the contrary, the <span>MIME type</span>
"<code>application/octet-stream</code>" when used <em>with</em>
parameters, e.g.
"<code>application/octet-stream;codecs=theora</code>", <em>is</em>
<span>a type that the user agent knows it cannot render</span>,
since that parameter is not defined for that type.</p>

<dl class="domintro">

<dt><var title="">media</var> . <code title="dom-navigator-canPlayType">canPlayType</code>(<var title="">type</var>)</dt>
<p>The <dfn title="dom-navigator-canPlayType"><code>canPlayType(<var
title="">type</var>)</code></dfn> method must return the empty
string if <var title="">type</var> is <span>a type that the user
agent knows it cannot render</span>; it must return "<code
agent knows it cannot render</span> or is the type
"<code>application/octet-stream</code>"; it must return "<code
title="">probably</code>" if the user agent is confident that the
type represents a <span>media resource</span> that it can render if
used in with this <code>audio</code> or <code>video</code> element;
to network errors, causing the user agent to give up trying to
fetch the resource</dt>

<dt>If the <span>media resource</span> is found to have <span
title="Content-Type">Content-Type metadata</span> that, when
parsed as a <span>MIME type</span> (including any codecs
described by the <code title="">codecs</code> parameter, if the
parameter is defined for that type), represents <span>a type that
the user agent knows it cannot render</span> (even if the actual
<span>media data</span> is in a supported format)</dt>

<dt>If the <span>media data</span> can be fetched but is found by
inspection to be in an unsupported format, or can otherwise not
be rendered at all</dt>

0 comments on commit ab03111

Please sign in to comment.
You can’t perform that action at this time.