"The WHATWG HTML 5 working draft has a specification for a 'video' element.I briefly mentioned in a previous post that I was working on implementing this tag natively in Firefox. The intent is to display Ogg Theora encoded video without needing any plugins...

"The patches in bug 382267 to add support for the WHATWG video and audio elements have been applied to the Firefox mozilla-central repository..."

"I've uploaded new builds of Firefox with experimental support for the WHATWG 'video' element. They are (compiled from this git commit)..."

Since last week's announcement of the YouTube and Vimeo beta versions which use HTML5's element, the Mozilla developers have been defending the fact that Firefox 3.6 cannot play the content on these betas even though it supports HTML5. The reason for the problem is that the HTML5 working groups decided not to specify which video codecs the tag would support.

"Some updates to the video element have landed and are now in the Firefox nightly builds..."

"The video element is used to embed video content in an HTML or XHTML document. The video element was added as part of HTML 5..." -- See also:
*Audio
*Using geolocation

"I wrote earlier about refactoring the HTML5 video patch to allow different backends. I've now added a patch for GStreamer support to bug 422540..."

"...User agents should support Ogg Theora video and Ogg Vorbis audio, as well as the Ogg container format..."

"The git repository has multiple branches which means a little more git usage is needed to get at the Ogg (and soon, GStreamer) backends. [...] By default the 'master' branch has a checked out working tree. Building this produces element support without any decoder. One approach to building the Ogg backend is to create a local branch with the commits from the remote branch origin/ogg and build that..."