W3C home > Mailing lists > Public > public-html@w3.org > March 2009

Re: <video> feedback

From: Simon Pieters <simonp@opera.com>
Date: Thu, 26 Mar 2009 09:36:28 +0100
To: "Ian Hickson" <ian@hixie.ch>, public-html <public-html@w3.org>
Message-ID: <op.urd4uxv3idj3kv@zcorpandell.linkoping.osa>
On Wed, 25 Mar 2009 23:11:53 +0100, Ian Hickson <ian@hixie.ch> wrote:

>> It seems more predictable and useful to fire an error event at the media
>> element at the point you find a <source> (or <video src>) that is not
>> supported. (Also more consistent with <img> -- without a src="" you
>> don't get an error event.) error.code could say MEDIA_ERR_NOT_SUPPORTED
>> instead, and the MediaError interface could gain another attribute (say
>> error.src) that is set to the value of .currentSrc at the time the error
>> occurred. (Since the algorithm is async authors can't just look at
>> .currentSrc since it might have changed before the event handler looks
>> at it.)
>
> The idea of the error event in this particular case is to let the page
> show a message, which would be overridden by the loadedmetadata event's
> handler, or some such. I suppose we could just fire an event for each
> unsupported resource, though... what are the other use cases?

Maybe the message would contain pointers to codecs for the failed videos.

-- 
Simon Pieters
Opera Software
Received on Thursday, 26 March 2009 08:37:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:44 UTC