Bug 13708 - Request: Support for <video> and <audio> elements
Summary: Request: Support for <video> and <audio> elements
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 523.x (Safari 3)
Hardware: Macintosh OS X 10.4
: P3 Enhancement
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-13 09:24 PDT by Ivo Emanuel Gonçalves
Modified: 2007-11-29 06:21 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivo Emanuel Gonçalves 2007-05-13 09:24:57 PDT
Hello,

Any ETA for when WebKit will have support for HTML 5's <video> and <audio> elements?  I believe the WebKit API is ready, but the OS X would have to support Theora and Vorbis to be compatible with the WHATWG specification.
Comment 1 Brady Eidson 2007-05-13 22:59:59 PDT
Putting aside for a moment the fact that HTML5 is nowhere near final, implementation of the video and audio elements does not require supporting ogg/vorbis/theora.
Comment 2 Mark Rowe (bdash) 2007-05-13 23:09:28 PDT
For what it's worth, in the current form the WHAT WG HTML 5 specification does say "User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format".  As Brady points out though, the HTML 5 spec is far from being final.
Comment 3 Brady Eidson 2007-05-13 23:25:52 PDT
My point was "should support" in a spec does not denote a requirement.  We could have a perfectly suitable implementation of audio and video as seen in this draft spec without having theora/vorbis codecs available.
Comment 4 Antti Koivisto 2007-11-12 14:00:54 PST
Initial <video> and <audio> support is in.
Comment 5 Christian Dywan 2007-11-29 02:16:40 PST
(In reply to comment #3)
> My point was "should support" in a spec does not denote a requirement.  We
> could have a perfectly suitable implementation of audio and video as seen in
> this draft spec without having theora/vorbis codecs available.

An important point of the spec is the ability to provide media without the need to care about portability issues. Ergo if no common codec is available most of the advantages of audio and video will be lost.
Comment 6 Mark Rowe (bdash) 2007-11-29 03:58:29 PST
That's an issue for the HTML and WHAT working groups to discuss.
Comment 7 Ivo Emanuel Gonçalves 2007-11-29 05:22:15 PST
> That's an issue for the HTML and WHAT working groups to discuss.

They already discussed it.  THe WHATWG, the W3C, and some of the browser makers voted to make Theora and Vorbis (of the Ogg multimedia framework) the baseline codecs.  Apple is attempting to go against the tide for no apparent reason.
Comment 8 Mark Rowe (bdash) 2007-11-29 05:29:30 PST
As previously mentioned, this is not the appropriate place to raise that issue.
Comment 9 Ivo Emanuel Gonçalves 2007-11-29 05:37:47 PST
> This is not the appropriate place to raise that issue.

I don't mind to create a separate ticket regarding this matter if that's what you are suggesting.
Comment 10 Mark Rowe (bdash) 2007-11-29 06:15:35 PST
It is not.
Comment 11 Mark Rowe (bdash) 2007-11-29 06:21:42 PST
To clarify a little:  the HTML 5 specification is currently a draft.  In its current state, it does not require implementations to support Theora.  As it is a draft, that may change in the future.  Discussion about requirements for implementation support of specific codecs should happen on either the HTML working group or on the WHAT working group mailing lists.  As WebKit relies on the platform for codec support, requests for further codecs should be directed to the platform vendor.  In case of the Mac the underlying platform is QuickTime and the appropriate method of raising such points is via the Apple bug reporting system at http://bugreport.apple.com/.