[html5] r5407 - [giow] (1) canPlayType('application/octet-stream') should always return ''.
whatwg at whatwg.org
whatwg at whatwg.org
Mon Aug 30 18:59:50 PDT 2010
Author: ianh
Date: 2010-08-30 18:59:49 -0700 (Mon, 30 Aug 2010)
New Revision: 5407
Modified:
complete.html
index
source
Log:
[giow] (1) canPlayType('application/octet-stream') should always return ''.
Modified: complete.html
===================================================================
--- complete.html 2010-08-31 00:35:32 UTC (rev 5406)
+++ complete.html 2010-08-31 01:59:49 UTC (rev 5407)
@@ -24502,16 +24502,19 @@
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 title="">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
+ <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 title="">application/octet-stream</code>" when used <em>with</em>
- parameters, e.g. "<code title="">application/octet-stream;codecs=theora</code>", <em>is</em>
+ 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>.</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>
@@ -24528,14 +24531,14 @@
<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. Implementors are encouraged to return "<code title="">maybe</code>" unless the type can be confidently
- established as being supported or not. Generally, a user agent
- should never return "<code title="">probably</code>" if the type
- doesn't have a <code title="">codecs</code> parameter.</p>
+ and it must return "<code title="">maybe</code>" otherwise.
+ Implementors are encouraged to return "<code title="">maybe</code>"
+ unless the type can be confidently established as being supported or
+ not. Generally, a user agent should never return "<code title="">probably</code>" if the type doesn't have a <code title="">codecs</code> parameter.</p>
</div>
@@ -46178,8 +46181,8 @@
there are no <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>,
then append an entry in the <var title="">form data set</var>
with the <var title="">name</var> as the name, the empty string
- as the value, and <code title="">application/octet-stream</code>
- as the type.</li>
+ as the value, and <code>application/octet-stream</code> as the
+ type.</li>
<!-- https://bugzilla.mozilla.org/show_bug.cgi?id=529859 -->
<li><p>Otherwise, if the <var title="">field</var> element is an
Modified: index
===================================================================
--- index 2010-08-31 00:35:32 UTC (rev 5406)
+++ index 2010-08-31 01:59:49 UTC (rev 5407)
@@ -24427,16 +24427,19 @@
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 title="">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
+ <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 title="">application/octet-stream</code>" when used <em>with</em>
- parameters, e.g. "<code title="">application/octet-stream;codecs=theora</code>", <em>is</em>
+ 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>.</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>
@@ -24453,14 +24456,14 @@
<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. Implementors are encouraged to return "<code title="">maybe</code>" unless the type can be confidently
- established as being supported or not. Generally, a user agent
- should never return "<code title="">probably</code>" if the type
- doesn't have a <code title="">codecs</code> parameter.</p>
+ and it must return "<code title="">maybe</code>" otherwise.
+ Implementors are encouraged to return "<code title="">maybe</code>"
+ unless the type can be confidently established as being supported or
+ not. Generally, a user agent should never return "<code title="">probably</code>" if the type doesn't have a <code title="">codecs</code> parameter.</p>
</div>
@@ -46103,8 +46106,8 @@
there are no <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>,
then append an entry in the <var title="">form data set</var>
with the <var title="">name</var> as the name, the empty string
- as the value, and <code title="">application/octet-stream</code>
- as the type.</li>
+ as the value, and <code>application/octet-stream</code> as the
+ type.</li>
<!-- https://bugzilla.mozilla.org/show_bug.cgi?id=529859 -->
<li><p>Otherwise, if the <var title="">field</var> element is an
Modified: source
===================================================================
--- source 2010-08-31 00:35:32 UTC (rev 5406)
+++ source 2010-08-31 01:59:49 UTC (rev 5407)
@@ -26268,19 +26268,19 @@
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
- title="">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
+ <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
- title="">application/octet-stream</code>" when used <em>with</em>
- parameters, e.g. "<code
- title="">application/octet-stream;codecs=theora</code>", <em>is</em>
+ 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>.</p>
<dl class="domintro">
@@ -26302,16 +26302,17 @@
<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;
- and it must return "<code title="">maybe</code>"
- otherwise. Implementors are encouraged to return "<code
- title="">maybe</code>" unless the type can be confidently
- established as being supported or not. Generally, a user agent
- should never return "<code title="">probably</code>" if the type
- doesn't have a <code title="">codecs</code> parameter.</p>
+ and it must return "<code title="">maybe</code>" otherwise.
+ Implementors are encouraged to return "<code title="">maybe</code>"
+ unless the type can be confidently established as being supported or
+ not. Generally, a user agent should never return "<code
+ title="">probably</code>" if the type doesn't have a <code
+ title="">codecs</code> parameter.</p>
</div>
@@ -51806,8 +51807,8 @@
title="concept-input-type-file-selected">selected files</span>,
then append an entry in the <var title="">form data set</var>
with the <var title="">name</var> as the name, the empty string
- as the value, and <code title="">application/octet-stream</code>
- as the type.</p></li>
+ as the value, and <code>application/octet-stream</code> as the
+ type.</p></li>
<!-- https://bugzilla.mozilla.org/show_bug.cgi?id=529859 -->
<li><p>Otherwise, if the <var title="">field</var> element is an
More information about the Commit-Watchers
mailing list