I predict that <video> will be very slow to catch on. The standard <object> tag from HTML4
solves this problem much more elegantly. Indeed, <object> is stated in the HTML4 technical
report to be preferable even to the widely used <img> tag. With <video>, the HTML5 working
group have taken a giant leap backwards into the dark old days of HTML3.
<object> allows the browser to choose from among a group of alternative content. <object>
would allow the web designer to give the browser a choice between Ogg Theora video, Flash
video, a still image, or explanatory text. This would be the best implementation because
people with FF3 would get the built-in video, people without FF3 would get Flash video, and
people without Flash would get the still image. People using a VT100 could read the text
instead. With the HTML5 <video> tag web designers will now need to hack up some kind of
javascript code to detect the presence of <video> support, and switch between Ogg and Flash as
needed.
http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.1
Posted Aug 8, 2008 8:09 UTC (Fri) by ekj (guest, #1524)
[Link]
img does too, with content-negotiation, which hardly anyone ever uses.
You can say img src="images/logo" and then tell Apache or IIS to do content-negotiation, that
is, send the format which the broweser prefers. (based on the ordering in the accept-header,
if I remember correctly)
So a browser that said Accept: image/svg, image/png, image/jpg, */* would get logo.svg (if
existing), whereas one without support for svg would get the png-one (if existing).
It's a real shame that neither this, nor language-negotiation is typically used for anything
at all. It's kinda neat.
Firefox to support Theora video
Posted Aug 9, 2008 18:11 UTC (Sat) by gerv (subscriber, #3376)
[Link]
The standard <object> tag from HTML4
solves this problem much more elegantly.
But browser makers who actually have to implement it hate it, and prefer more specific tags (see discussion on the WHAT-WG mailing list, and the rationale for creating <video> and <audio>).
It seems that the WHAT-WG goes for pragmatism, what works and what can be coded and deployed easily over theoretical purity. That's one of the things that distinguishes it from the W3C (although the joint working of the two organisations may indicate a change there). This approach has the advantage of things actually getting implemented.
Firefox to support Theora video
Posted Aug 9, 2008 18:48 UTC (Sat) by jwb (guest, #15467)
[Link]
I just did some tests with MSIE and it seems that <object> inside <video> does what you'd want
on that browser, so my objection is wrong. I tested this before but I must have screwed it
up. I now don't think you'd need any kind of javascript to sniff the <video> tag since MSIE
just ignores it and parses down to <object>.