As stated in the HTML5 specification: "It would be helpful for interoperability if all browsers could support the same codecs."
Firefox and Opera are already working on native support for Ogg Vorbis / Theora. As far as I know there are open licence/patent issues to be solved first. However, it might be useful to have native support for at least one codec on all WebKit platforms.
I've created this bug report since I couldn't find one that addresses this issue.
What do you mean by "native codec support"? It's not clear what you're requesting in this enhancement request.
I guess this means that video decoder plugs right into rendering engine, just like we have jpeg and png image decoder interfaces present in WebKit.
That's right, native support for e.g. Ogg as WebKit supports SVG, PNG, JPG, GIF without a plugin. This is what is stated in  and .
I will put it into other words (cf. ): "The goal with WebKit is to make Ogg Vorbis/Theora a first-class audio/video format, so that it can be used anywhere you might use a video or audio. In other words, all of the following should be possible: <video src=videosample.ogg></video> <audio src=audiosample.ogg></audio> without using plugins."
Of course you could exchange Ogg Vorbis/Theora with other formats.
So, would this bug be better titled as "Please implement Ogg Vorbis and Theora support directly in WebKit"? I don't see how that would help having them supported in shipping products though.
Could you please explain why WebKit doesn't support Ogg Vorbis? Latest FF, Opera and Chrome — all do; playing audio on the web would be as simple as including audio element referencing Ogg -based audio file... if not for webkit.
Vendors of WebKit-based software can always support Ogg Vorbis/Theora via other mechanisms, as evidenced by both Chrome (which has it built-in) and Safari (which has such support once you install appropriate codecs for QuickTime).
Since having the code in WebKit repository has no effect on user experience, this is not a valid enhancement request. A vendor could legitimately make such a request if it made sense for them for technical reasons, but no vendor has expressed such desire yet.
There is nothing political about having the code in WebKit or not, and having it in WebKit can't make it magically appear in actual Web browsers.
I'm marking this bug as WONTFIX for now. It can be reopened if a technical reason to address it is found.
Thank you. This clears things up.