Thursday, November 08, 2007

Opera has a new Video enabled build

Opera is making a call for video on the web, releasing an experimental build with video support modelled on the latest WHATWG specification.

Their post has some examples to try out and instructions on how to use the <video> element.

Their examples work quite well in the latest video enabled build of Firefox too. Thanks to help from Robert O'Callahan it now has support for the 'controls' attribute. There's no more need for JavaScript buttons to activate video. I've also implemented some of the events. This code is in the git repository.

Some very experimental binary builds if you want to try things out:
Be aware that these are builds from a random point in the Mozilla CVS tree, with the Video patch applied. I don't guarantee they'll work for much more than demonstrating video support and it's very likely to contain bugs. That said, I run these builds often.

Try out the demo's that Opera have done, or the one's on my test page.

It's very cool to see video support using patent free formats running on more than one browser, with simple HTML that can be embedded by anyone. Thanks Opera!

Categories: firefox,

Labels:

10 Comments:

Anonymous Felix said...

Hi Chris,

Will there also be RTP video streaming support?

1:06 AM  
Blogger jmdesp said...

Unfortunately Roc is talking about removing this completely from Fx 3, becasue there won't be time to integrate the latest WHATWG specification.

I think it's a bad decision. There's a difference between deliberately including a non-compatible features months, years after the standard is out and never update it to the standard, and having one release that incompletely respect the standard because of time constraint. I think it would be perfectly OK to have a video tag in Fx 3 that is only a partial support of the video spec, just like you fortunately didn't wait for Fx SVG implementation to support all of SVG to ship it.

2:04 AM  
Anonymous Dao said...

Shipping something that violates the spec could turn out to be a bad idea. However, if you could implement a subset of the spec in a solid way, I think that's something to consider seriously. The fact that Opera's examples work with your custom build is certainly a good sign.

3:00 AM  
Anonymous Anonymous said...

I think open, royalty free format support is too critical to not ship <video>. We're at a critical point in the development of video on the web. Don't miss this window of opportunity. Please fine a way.

5:02 AM  
Anonymous Flavio said...

Why a new "video" element? Wasn't "object" with right mime type perfectly appropriate for video too?

A standard javascript interface for video could be also defined to script the "object". So, again, what's the point for the new tag?

5:23 AM  
Blogger Robert said...

felix: No. Although if someone implements it we'd certainly consider patches.

flavio: that question was extensively discussed in the WHATWG mailing list. I suggest you look there.

9:26 AM  
Blogger Martijn said...

So when I have:
video controls="" src="A_New_Computer--small.ogg" id="myVideo"Theora decoder not found/video
on a page locally and that ogg file doesn't exist, then I crash with the build when clicking on the 'Play' button.

This looks really awesome. Nice work, Chris!

12:46 PM  
Blogger Chris Double said...

Oops, thanks for that report. I'll fix it.

12:51 PM  
Anonymous Anonymous said...

while I'm sure these are very early days, I have to say these demos are quite horrible without buffering control.

I personally will not view WMP plugin video until I set the buffering to 30 seconds and that way I can get quite reasonable continuous playback.

Each and every one of these video demos I tried suffered from extreme staggering.

I'm glad it's not going to be in Fx 3 because it looks about a year off being fully mature and ready which will make it sweet for Fx4.

2:52 PM  
Blogger Chris Double said...

The builds linked here have no buffering control as you say. That's the only reason they stutter. Playing locally is fine.

Previous builds did have simple buffering control but I've removed it pending a refactoring of that area to do with the addition of the recently added events.

Such is the cost of doing 'in between builds' on work in progress code.

3:01 PM  

Post a Comment

<< Home