Bug 13708
| Summary: | Request: Support for <video> and <audio> elements | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ivo Emanuel Gonçalves <justivo> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Enhancement | CC: | christian, mrowe, sylvain.pasche |
| Priority: | P3 | ||
| Version: | 523.x (Safari 3) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
Ivo Emanuel Gonçalves
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brady Eidson
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.
Mark Rowe (bdash)
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.
Brady Eidson
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.
Antti Koivisto
Initial <video> and <audio> support is in.
Christian Dywan
(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.
Mark Rowe (bdash)
That's an issue for the HTML and WHAT working groups to discuss.
Ivo Emanuel Gonçalves
> 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.
Mark Rowe (bdash)
As previously mentioned, this is not the appropriate place to raise that issue.
Ivo Emanuel Gonçalves
> 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.
Mark Rowe (bdash)
It is not.
Mark Rowe (bdash)
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/.