[whatwg] Media resource fetch algorithm reporting failure

Chris Pearce chris at pearce.org.nz
Thu Sep 16 15:48:35 PDT 2010

  In the media element resource fetch algorithm [1], there's this step:


If the media data 
cannot be fetched at all, due to network errors, causing the user agent 
to give up trying to fetch the resource [or]
If the media resource 
is found to have Content-Type metadata 
that, when parsed as a MIME type 
(including any codecs described by the |codecs| parameter), represents a 
type that the user agent knows it cannot render 
(even if the actual media data 
is in a supported format) [or]
If the media data 
can be fetched but is found by inspection to be in an unsupported 
format, or can otherwise not be rendered at all


      The user agent should cancel the fetching process.


      Abort this subalgorithm, returning to the resource selection


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?

Chris Pearce.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100916/a6d43dbd/attachment-0002.htm>

More information about the whatwg mailing list