W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] <video> element error handling

From: Nathanael Ritz <nathanritz@gmail.com>
Date: Tue, 17 Mar 2009 23:58:46 -0600
Message-ID: <f3f6c7820903172258i66dd023bi5a82c4305da887c7@mail.gmail.com>
Hi there,

When I was playing around with the <video> element today I noticed my
browser didn't seem to handle errors in a way that was very useful.
Specifically, I am using the Safari 4 beta on Windows Vista. When I tried
putting the page together, my markup was coded in this way:

<video src="firefox.ogv" autoplay><embed id="VideoPlayback"

style="width:344px;height:285px;" allowFullScreen="true"
type="application/x-shockwave-flash" /></video>

I was trying to grab the video from the WHATWG demo page but I forgot that I
copied a relative link. So without knowing that the video would not work in
the first place, I tried opening up a valid HTML 5 page with this particular
set of markup. It didn't play. But not only did it not play, Safari refused
to do anything to tell me something was wrong. Instead I just saw a blank

When I tried a random mp4 file, I got a green box, but no playback. When I
finally learned I was using a relative link and put in the full URI for the
firefox.ogv video, it still didn't work.

My observation is that if it is not already recommended in the spec,
browsers should offer some sort of indication it could not use whatever file
format it was supplied or received something like a 404 from the server.
Whether it's a broken video box icon, or automatically reverting to the
fallback content within the <video> element (if it exists), I think there
should be some sort of warning or indication of a failure.

What kind of error handling does the <video> element have?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090317/09ae07df/attachment.htm>
Received on Tuesday, 17 March 2009 22:58:46 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:10 UTC