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

[whatwg] Some <video> questions

From: Geoffrey Sneddon <foolistbar@googlemail.com>
Date: Tue, 29 Jan 2008 17:49:58 +0000
Message-ID: <806140C9-3702-47DE-96F7-4B8D4375360C@googlemail.com>

On 28 Jan 2008, at 23:32, Charles wrote:

>> The <video> element offers an interface to the native media
>> playback capabilities of the platform.
>
> The browser platform (e.g. WebKit), the multimedia platform (e.g.  
> QuickTime)
> or the OS platform (e.g. Mac OS X)?

Whatever the browser chooses to use. In WebKit's case, this is the OS  
(so QT on OS X, DirectShow on Windows, and GStreamer on GTK). Presto  
(in Opera) provides its own decoder (for Ogg/Vorbis/Theora, likewise  
does Gecko.

>> It is not a plug-in mechanism and it is not suitable for embedding
>> things like Flash or Silverlight.
>
> So for Safari on both Macintosh and Windows, is Apple's intent that  
> <video>
> will only work for formats supported by QuickTime?

Apple's intent, as far as I'm aware, is to use the natively supported  
multimedia support of a given environment (as WebKit isn't for  
multimedia). Also, as Henri has already said, QuickTime supports  
plugins itself.

> And given that little internet content targets QuickTime, who  
> exactly will
> be using the <video> tag?

There is a _huge_ amount of content on the web that uses MPEG-4, which  
QuickTime supports (note that on Windows DirectShow doesn't support  
MPEG-4 out of the box, and AFAIK only supports MPEG-1 and WMV (for  
video)). There's also still a large amount of content that relies on  
the QuickTime container format (.mov), even if the content is MPEG-4  
(whose own container is based on the QT one).


--
Geoffrey Sneddon
<http://gsnedders.com/>
Received on Tuesday, 29 January 2008 09:49:58 UTC

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