W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2012

[whatwg] video element not ready for prime time

From: Francis Boumphrey <boumphreyfr@gmail.com>
Date: Thu, 12 Jan 2012 12:46:08 -0500
Message-ID: <CAN1jwS7XOG4j_fjp5MuRgVDWyyZ2ZkM_1Vj=EZqedn34-44o8w@mail.gmail.com>
A few comments about the <video> element from the point of view of an HTML
author. Currently it is not particularly useful, and there is nothing to
encourage me to use it rather than <embed>

Firstly if I use a video with the src attribute

e.g. <video src='myvideo.mp4' controls>

and my user agent does not support the format, all I get (in my versions of
Opera and Firefox) is a blank screen. No message (as I would get with
<embed>) and as far as I can see there is no way for me as an author to
know that the video is not being played so I cannot code a 'write around'.

The option is to make several formats of the same video, e.g. myvideo.mp3,
myvideo.mp4, myvideo.ogg etc. and place them in child <source> elements in
the hope that one of the formats will be displayed.

Even here I have a problem. In which order does the user-agent check the
source files (in Chrome it seems to be in the order in which they are
written, but there is no guidance here in the spec.

Also will my user agent down-load the file that it cannot play, thus using
up band-width?

I think these questions need to be resolved before authors will start using
<video> for regular pages.

The same comments go for the <audio> element.

Frank Boumphrey
Received on Thursday, 12 January 2012 09:46:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:10 UTC