[ close ]
Help Upgrade the Web: Download Firefox 3.5

two cool things: ogg support in mozilla and canvas for IE

Two cool things coming out at the summit today.

First, Mozilla is committing to include native support for OGG video and audio in its next release that includes support for the video element tag. (Very likely to be Firefox 3.1 if there no huge change in course.) The code landed for ogg support last night. I suspect that the effects of this will take a long while to be felt but it’s a great first step in bringing open video to the web by delivering it to a couple hundred million people around the world.

Second, Vlad has written a native ActiveX control for IE that implements the canvas tag. In order to use it you just have to include a little .js snippit in your page and object tag that pulls in the control. It’s fully scriptable, of course, and the source code will be made available for other people to see and improve. With this control it means that canvas will be available on all major browsers, even though Microsoft has yet to implement it. We’ll have more details once Vlad makes a post on it.

Update: Vlad has made a complete post about the IE Canvas code.

Update 2: Chris Double has a post about the Theora backend.

  1. Ralph Giles’s avatar

    Very, very good news! It’s great to see this.

  2. Cyde Weys’s avatar

    It’s great that we finally have integrated video support for a Free Software codec. Finally, a better alternative to Flash players — woohoo!

  3. Anonymous’s avatar

    Allegedly, Microsoft has not implemented the canvas tag because Apple has claimed rights over some of the related IP

    http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2007-March/010129.html

  4. Christopher Allan Webber’s avatar

    Wahoo! Fantastic, I’ve been hoping to hear of this for ages!

    And nice job improving IE for the IE team! ;)

  5. skierpage’s avatar

    Very cool, I made a test page http://www.skierpage.com/moz_bugs/test_audio_video_tags.html using some OGG files from Wikimedia Commons.

    Works great, though autoplay=”false” and controls=”true” don’t seem to work.

  6. Anders Feder’s avatar

    The canvas tag, while definitely a better option than Flash, seems mildly suspect – I hope it won’t sway people away from styling their content with CSS and back to hardcoding content semantics into e.g. Javascript (or however the canvas is controlled).

  7. David Gerard’s avatar

    Wikimedia/Wikipedia, by the way, pushes Theora/Vorbis BIG TIME. Basically because they’re the free formats that are acceptable on Wikimedia Commons. The FUDmeisters may have gotten them excluded by name from the HTML5 spec, but they can be taken as read and Apple and Nokia can just play catchup.

  8. hdh’s avatar

    @skierpage: the boolean attributes should be controls=”" or controls or controls=”controls”, I guess to avoid confusion between on/off/true/false in different context

  9. Havoc’s avatar

    IE Canvas control = hell yes

  10. Mark’s avatar

    I am obviously in the minority here, but I believe the whole point of Firefox was to be a smaller, faster, simpler browser. I don’t think having built-in video codecs is a good idea, at all.

    I have nothing against video support, nor Theora. And I very much approve of open standards/source technologies to fight against proprietary ones (like MPEG, Flash, etc) But those would best be handled by external applications as plugins or helper apps!

    Keep it simple. Keep it clean. The less code the:

    1) less download size
    2) easier to compile
    3) easier to port to other platforms
    4) fewer bugs
    5) less possible security venerabilities
    6) less memory used
    7) faster loading/startup time
    8) more customizable

  11. blizzard’s avatar

    Haha, finally made Havoc happy. My job is done here.

    On the download size question it’s always a trade off. We’ve got a very small download size (go compare FF for Windows and Safari for Windows as examples) and the OGG stuff isn’t all that big. But it’s not zero, either. Video support is worth that cost.

    The fact is that video is part of the web. Right now it’s done with flash. We should be doing it as part of the browser. So go compare the decoders for OGG with a flash download if you want to compare download sizes.

  12. उन्मुक्त’s avatar

    Great! I have been podcasting in ogg format for two years and my listners always had difficulty in listening it.

  13. Roy Schestowitz’s avatar

    Thank you for this! (Ogg)

  14. Dan Kegel’s avatar

    That’s fantastic news!

    Next step: how about adding Schroedinger support? That’s a pretty good free video codec, too. Might even be higher quality.

  15. Simon Holm Thøgersen’s avatar

    I’ll second Dan Kegel’s question on what about adding Dirac video support through the Schroedinger implementation?

    Great start with Theora for sure though :)

  16. blizzard’s avatar

    I don’t know what the status of Dirac support is. But keep in mind that the backends here are pluggable. If you want it supported the first step would be to talk to Chris Double. Step two is to open a bug and step three is to start writing code.

    On Linux with a gstreamer backend if the system has Dirac support you’re going to get it anyway. But if we’re able to ship mac + windows support along with the browser that’s where the real impact will be. So you have to worry about those as platforms.

  17. dave’s avatar

    What’s with all the ‘bloat’ trolling regarding Theora, here and elsewhere? It’s the 21st century and video is part of the web now, get over it.

    Chris already made this same point but I’d like to echo and emphasise it. Go down this list posted earlier and mentally compare Open Source built-in Theora versus the proprietary, closed source, non-64-bit, unavailable for your obscure platform or handheld, punch-the-monkey advertising platform that everyone currently uses for video and audio streaming.

    > Keep it simple. Keep it clean. The less code the:

    1) less download size
    2) easier to compile
    3) easier to port to other platforms
    4) fewer bugs
    5) less possible security venerabilities
    6) less memory used
    7) faster loading/startup time
    8) more customizable

    For those not keeping score, Theora wins — big time. And don’t forget vorbis too!

  18. Chris Double’s avatar

    For those asking about Dirac support, yes I’m looking at it. It would be dirac embedded in an Ogg container, using Vorbis for the audio. The ideal solution would be for this to be added to the Oggplay library I use and I’ll liase with annodex to see if anyone else is already doing that (in which case we’d get it for free essentially).

  19. wow’s avatar

    > I don’t think having built-in video codecs is a good idea, at all.

    Disagree. Add them, but only as few as possible -> Theora & Dirac. IIRC Theora decoder compiles to cca 64 KiB … cca 1% of FFX size, definitely worth the benefit.

    But why not brew a FFX-light without AV, JS, spell-check (BTW: stop underlining the word “Theora” !!!) … etc. ?

    > What’s with all the ‘bloat’ trolling regarding Theora, here and elsewhere?
    > It’s the 21st century and video is part of the web now, get over it.

    You are very wrong here. Not Theora is the bloat, the Adobe “Flash” mess + JS + WMW + MPEG-H-xxx + all_other_silly_codecs is the bloat. Get the facts right !

  20. William Lacy’s avatar

    Firefox 3.1 is a blessing for OGGTV.com. OGG/THEORA content on the web, just got super-easy for everyone.

  21. Tom’s avatar

    You guys rock!

    Ogg Vorbis and Theora are a great great start!

    But I also think to be really competitive you will need Dirac (Schrödinger?) at some point.

    @Chris: I am totally excited that you are looking at it.

    Maybe Mozilla could convince Google to incorporate those codecs in Chrome too. And then Google could convince Apple ;)

    And then the world could convince Microsoft … Aww, dreaming is so nice ;)
    Make Youtube HD dirac only!

  22. Michael

    Cool. Now to Opera and WebKit.