<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ah I see that we will fire an error event when we return to the
resource selection algorithm in this case, since we didn't abort the
resource selection algorithm. Never mind!<br>
<br>
Chris P.<br>
<br>
<br>
On 16/09/2010 3:48 p.m., Chris Pearce wrote:
<blockquote cite="mid:4C929EC3.3060308@pearce.org.nz" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
In the media element resource fetch algorithm [1], there's this
step:<br>
<br>
<quote><br>
<dl class="switch">
<dt>If the <a moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#media-data">media
data</a> cannot be fetched at all, due to network errors,
causing the user agent to give up trying to fetch the resource
[or]<br>
</dt>
<dt>If the <a moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#media-resource">media
resource</a> is found to have <a moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/urls.html#content-type"
title="Content-Type">Content-Type metadata</a> that, when
parsed as a <a moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#mime-type">MIME
type</a> (including any codecs described by the <code
title="">codecs</code> parameter), represents <a
moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#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 moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#media-data">media
data</a> is in a supported format) [or]<br>
</dt>
<dt>If the <a moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#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>
</dl>
<ol>
<li>
<p>The user agent should cancel the fetching process.</p>
</li>
<li>
<p>Abort this subalgorithm, returning to the <a
moz-do-not-send="true"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#concept-media-load-algorithm"
title="concept-media-load-algorithm">resource selection
algorithm</a>.</p>
</li>
</ol>
</quote><br>
<br>
Why don't we dispatch an error event to the candidate source child
we were loading from, or the media element if it was loading from
a source attribute, in this case? We dispatch error events in the
resource selection algorithm if the source child has an
unsupported type, how is this significantly different?<br>
<br>
<br>
Regards,<br>
Chris Pearce.<br>
<br>
[1]
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#concept-media-load-resource">http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#concept-media-load-resource</a><br>
</blockquote>
<br>
</body>
</html>