Video.js Blog

Video.js 4.0 now available!

Thu, 09 May 2013 13:10:00 -0400

Today we’re releasing Video.js 4.0, which is the most solid, lightweight, and I dare say prettiest version yet. It’s available for download, on Github, and hosted for free on our CDN.

Version 4.0 received the most community collaboration of any previous version, which speaks to the growing strength of the JavaScript community, the growing popularity of HTML5 video, and an increase in Video.js usage. Over the last year the number of sites using Video.js has more than doubled, and each month there are over 200 million hits to the CDN-hosted version alone! Thank you to all of the Video.js community members for contributing code and filing bug reports.

This version is also a milestone in that it’s the first version released since Brightcove acquired Zencoder last year. For those who missed the announcement, it was a very good thing for Video.js. In the past, Video.js was a side project for Zencoder that I maintained on top of my regular responsibilities (as if startup life isn’t exciting enough). Post-acquisition, Brightcove has not only put me full-time on Video.js, but the Brightcove video player team has become contributors to the project. The Brightcove team is probably the most experienced video player team in the world, supporting the most advanced video technology, for the biggest brands, across all the devices. It’s been a privilege to work with them and they’ve made major contributions to this version.

4.0 Major Feature Summary:

Improved performance through an 18% size reduction using Google Closure Compiler in advanced mode

Greater stability through an automated cross-browser/device test suite using TravisCI, Bunyip, and Browserstack.
New plugin interface and plugin listing for extending Video.js
New default skin design that uses font icons for greater customization
Responsive design and retina display support
Improved accessibility through better ARIA support
Moved to Apache 2.0 license
100% JavaScript development tool set including Grunt

Improved Performance

With version 4.0, performance was our top priority, and a major factor of performance is the time it takes to load the library. What would seem to be minor size reductions can have a big impact, especially when a library will be loaded millions of times a month all over the world. We chose to use Google’s Closure Compiler because its “advanced mode” currently provides the most aggressive options for code minification, and so far we’ve seen an 18% reduction in code size, with the potential for more.

Closure Compiler also claims to rewrite code for better runtime performance, though we haven’t had a chance to benchmark this yet.

Some preliminary load-time benchmarking* shows:

Player load times in under 50 milliseconds
Playback start times in under 150 milliseconds
Actual video playback seen in under 0.5 seconds (using a CDN hosted MP4)

*Initial tests used Chrome with an empty cache on a modern MacBook Pro with a Wi-Fi connection. More formal testing to follow.

Greater Stability

Automated cross-browser, cross-device testing is the Holy Grail of testing for a JavaScript library. While building version 4.0, we’ve been able to reach that goal through the use of a number of tools, including:

TravisCI - Automatically runs unit tests through PhantomJS on every pull request made to the Video.js source code
Bunyip + Browserstack - Allows us to run tests in cloud-hosted instances of any browser from IE6 to the latest Chrome, and also a wide range of iOS and Android devices.

This ability to easily run tests across environments before any new release will give us more protection against regressions, and can allow for a faster feature release cycle.

New Plugin Interface

The new plugins API allows developers to more easily add custom features to Video.js. The API works similarly to the jQuery plugin interface, giving developers access to add to or overwrite any piece of Video.js. Once a plugin has been created, it can be shared on the Video.js plugin list page on the wiki.

New Default Skin

With help from the Brightcove UX team, we’ve created a new default skin that’s simpler, more polished, and more customizable. One of the most interesting features is that we’ve moved from using images for icons to font icons. The use of font icons allows you to change the color and size of the icons simply by changing a CSS value. You can see an example of this on the Video.js homepage.

Improved Accessibility

Greg Kraus, a Video.js community member from NCSU.edu, did some great work testing and improving Video.js accessibility through better use of ARIA roles. The changes make it so keyboard-only users, screen reader users, and voice-interface users will be able to interact with the video player. UPDATE: Read more in Greg’s blog post.

Moved to Apache 2.0 License

Earlier versions of Video.js were released under the LGPLv3 license. LGPL often gets confused with its stricter sibling, GPL, which requires that all code the software touches must also be open source. Video.js is meant to be open and free to use in all contexts, and we want that to be clear, so version 4.0 is now released under Apache 2.0, the same license Twitter Bootstrap is released under.

100% JavaScript Tool Set

Previously Video.js used Ruby for development tools, including Rake for deployment tasks, and zenflow–an internal Zencoder tool that builds on gitflow for development process workflow. With 4.0 we’ve moved to Grunt for tasks and we’re building out a tool similar to zenflow in Node.js.

Videojs.com Now Open Source

As part of this release we’ve also made the Videojs.com website open source. So if you see something that should be added or fixed, fork it.

What now?

Even with all of the updates listed above, this is simply a jumping-off point for what will be an exciting year for Video.js. We’re continuing to improve performance, multi-platform stability, and customizability through plugins and skins. Members of the community have already started work on plugins for some of the more requested features, like playlists, analytics, and advertising.

Follow @videojs or sign up for our newsletter to stay up-to-date on new features and roadmap updates.

If you’d like to get involved in the project, check out our contributing guide.

Cheers,
-heff

Repo Moved!

Mon, 06 May 2013 16:56:59 -0400

In preparation for the next version we’ve moved the source code repository from github.com/zencoder/video-js to github.com/videojs/video.js

If you have a local clone you can update your clone’s upstream URL with:

git remote set-url upstream git://github.com/videojs/video.js.git

The relationship between your fork (e.g. github.com/you/video-js) should still be intact, including any pull requests.

Cheers,
-heff

Site and Support Updates

Thu, 15 Nov 2012 14:54:18 -0500

After a brief hiatus of helping Brightcove and Zencoder come together, I’m moving full time to developing and supporting Video.js. Thank you to everyone who has continued to commit code and help out in the forums.

As part of this move I’m trying to optimize the tools used for video.js project management and support. The first big change is that the forums are being replaced with Stack Overflow (tag with “video.js”) and Github Issues.

Over the last few years Video.js has become more popular than I ever expected, and at the same time Stack Overflow has come up as an incredible tool for supporting developer communities. So along with many other projects like Facebook, Android, and HTML5 Boilerplate, I’m excited to move support to Stack Overflow’s awesome tool and community. I’ll be leaving the forums up for bit but from here forward please post questions to Stack Overflow and use the “video.js” tag.

I’ve also begun cleaning up and organizing the Github Issues for Video.js, which previously existed, but issues were split between the forum and Github. If you find specific bugs with video.js please submit them there.

On the project management side of things I’ll be using Trello, and exposing boards so others can see the progress of development.

I’m also paring down the site and moving more complex sections to other services that can better handle them. I’ve already moved the blog to Tumblr, and I’m moving the docs to the Github repo, which has built-in docs formatting.

For those starting an open source project today, you can look at this as my guide to supporting an open source project. I wish I would have know to do all this when I started on Video.js.

More project updates coming soon.

Cheers,
-heff

Brightcove Acquires Zencoder

Thu, 26 Jul 2012 00:00:00 -0400

Today, Zencoder announced that it is being acquired by Brightcove, the leading online video platform (OVP). You can read more on the specifics in the Zencoder blog post and press release, but I also wanted to be clear on what this means for Video.js. As you may know, Video.js was created by me (Steve Heffernan, Co-founder of Zencoder) and Zencoder continues to be its core contributor and sponsor (like 37signals to Rails or Joyent to Node.js).

This acquisition means only great things for Video.js. To quickly summarize, Video.js will continue to be a free and open source video player & framework, and Brightcove will be investing more in Video.js than Zencoder ever could.

I wrote the first version of Video.js in early 2010 during Zencoder’s time in Y Combinator (while secluded in our rented house deep in the Santa Cruz mountains). Over the past few years I’ve continued to build the library and pull in contributions from other Zencoder team members and the community, but only on the side of my ongoing Founder and VP of Marketing duties at Zencoder. While Video.js has continued to gain popularity among developers and is now being used on over 25,000 websites, there’s still work to be done and room to grow. So one of the more significant changes that will be happening is that Brightcove will be putting me on Video.js full time, freeing me up to work on the core of the project and to better support the Video.js community, both users and contributors.

Beyond this, Brightcove has a first-class player development team backing their platform’s video player. While the specifics of how the two teams and players will work together are still being discussed, we have agreement on our philosophies and views about where player technology is going. This combined knowledge and collaboration is sure to have a positive impact for both players.

While the additional resources will have a big impact, the best open source software projects only got to where they are through the contributions of developers in the community. So if you’ve previously been cautious to dig into the source or push back a specific feature or bug fix, I hope this news only helps encourage you to jump in and help make Video.js the best resource for working with video in the browser.

There will be more info to come as things progress, but please feel free to ask any questions in the comments below.

Cheers,

Steve & The Zencoder Team

Version 3.2 Update

Fri, 23 Mar 2012 00:00:00 -0400

First of all, check out the new video tag builder. The previous version of this site had an embed code builder, and people were pretty disappointed that the new site didn’t. So I’m happy to announce that it’s available again, now as an HTML5 video tag builder that could probably be used outside of Video.js, it includes track tags, and even lets you test the settings. Let me know if you have any feedback on it.

The most notable change in this release is probably the completely overhauled <track> tag support.

https://gist.github.com/4092295.js?file=html5-track-tag.html

The new version supports subtitles, captions, and even chapters. When you include tracks of different kinds, Video.js will automatically create menus in the player where users can select the language to display, or which chapter to jump to. Video.js also now supports the new WebVTT text format, which is not far off from the previously supported WebSRT format but did take some tweaking in the parser. Not all WebVTT placement features are supported yet, but the basics of displaying text are, and we’ll be working to get more WebVTT features built in.

Additionally there was work done to make some API methods accessible earlier. For any method that isn’t a getter (returns a specific value from the player), if you call the method before the playback technology (HTML5/Flash) is ready, it will now cache the call until it is ready. So where previously you might have had to wait for the ready callback:

https://gist.github.com/4092295.js?file=wait-for-ready.js

You could now do:

https://gist.github.com/4092295.js?file=no-wait-for-ready.js

Again, that’s just for methods where you are setting a value or triggering an action. If you try to get a value back like myPlayer.duration(), you’ll get nothing until the player is ready.

One other feature that was requested in the forums was automatically translating relative video URLs to absolute URLs for the flash fallback. This was an issue with the CDN hosted version which involved loading a remote SWF file which didn’t have the same context as the player. Before we would just tell people to use full URLs (http://) but that shouldn’t be an issue anymore.

Thanks to everyone that’s helped contribute code lately, and apologies for any long response times in the forums as I continue to try to push out code.

Here’s the full change log for the release.

3.2.0 / 2012-03-20 / baxter

Updated docs with more options.
Overhauled HTML5 Track support.
Fixed Flash always autoplaying when setting source.
Fixed localStorage context
Updated ‘fullscreenchange’ event to be called even if the user presses escape to exit fullscreen.
Automatically converting source URL to absolute for Flash fallback.
Created new ‘loadedalldata’ event for when the source is completely downloaded
Improved player.destroy(). Now removes elements and references.
Refactored API to be more immediately available.

Cheers,
-Heff

Version 3.1 Update

Mon, 30 Jan 2012 00:00:00 -0500

This is the first release since the initial 3.0 launch, aside from some hotfixes that went out immediately. It includes a number of fixes for things that users in the forums found right off the bat.

One feature that’s optional for testing in this release is iFrame Mode for Flash. One the of the unique things about Video.js is we haven’t built any controls into our Flash player, and instead use HTML and CSS to create the controls for the Flash side as well. This keeps the experience consistent and the Flash player very lightweight, however there’s a number of issues that you run into with Flash when you take an approach like this. If you’ve ever tried to resize the parent of a Flash object, or hide a Flash object and then show it again, you’ve probably run into the issue of Flash reloading in Firefox. This is a bug that’s been in Firefox for quite a long time however it looks like it might be fixed by version 13 (currently 9). To add on top of this, with the new browser fullscreen API, the other browsers now also reload Flash when you go to native fullscreen.

We’ve found a bit of a fix where if you embed the Flash object in an iframe first, it can get around the reloading in some of these cases. So in the new version there’s an option to turn this on and try it.

https://gist.github.com/4092929.js?file=iframe-mode.js

We’ll be doing some more testing to make sure it’s stable before we push it out to everyone.

Here’s the full change log for the release.

3.1.0 / 2012-01-30 / leonardo

Added CSS fix for Firefox 9 fullscreen (in the rare case that it’s enabled)
Replaced swfobject with custom embed to save file size.
Added flash iframe-mode, an experimental method for getting around flash reloading issues.
Fixed issue with volume knob position. Improved controls fading.
Fixed ian issue with triggering fullscreen a second time.
Fixed issue with getting attributes in Firefox 3.0
Escaping special characters in source URL for Flash
Added a check for if Firefox is enabled which fixes a Firefox 9 issue
Stopped spinner from showing on ‘stalled’ events since browsers sometimes don’t show that they’ve recovered.
Fixed CDN Version which was breaking dev.html
Made full-window mode more independent
Added rakefile for release generation

Cheers,
-Heff

Video.js Version 3.0!

Tue, 10 Jan 2012 00:00:00 -0500

After months and months of work we’re happy to announce Video.js version 3.0. Some of the exiting new features include:

Same HTML/CSS Skin for both HTML5 and Flash video
Super lightweight Flash fallback player for browsers that don’t support HTML5 video
Free CDN hosting by Level3 A lot more releases and developments are on their way!

Cheers,
-Heff

Lynda.com HTML5 Video Tutorial Released

Fri, 17 Jun 2011 00:00:00 -0400

I recently filmed a series of HTML5 video tutorials for Lynda.com, a really great service for online training. It was a great experience, and the videos are now available for viewing. You can get a 7-day free trial here and check them out. Let me know if they’re helpful at all.

-Heff

How are you using video.js?

Tue, 07 Jun 2011 00:00:00 -0400

I’d love to hear where and how people are using video.js. If you’re using it somewhere, leave a note/link in the comments.

Cheers,
-Heff

New MPEG LA WebM/VP8 Patent Pool

Fri, 11 Feb 2011 00:00:00 -0500

One of the things that browser and device vendors stand behind when deciding to support MP4/h.264 over Google’s Webm video format and VP8 codec, is that while VP8 is open source, it may still be encumbered by patents. So far none of these submarine patents have surfaced, but now MPEG LA has put out a call, and hopes to form a patent pool that would create a license for VP8, and essentially put a price on it. In Google’s own license, it says:

“If you or your agent or exclusive licensee institute or order or agree to the institution of patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that this implementation of VP8 or any code incorporated within this implementation of VP8 constitutes direct or contributory patent infringement, or inducement of patent infringement, then any patent rights granted to you under this License for this implementation of VP8 shall terminate as of the date such litigation is filed.”

So if you claim VP8 infringes on a patent and sue, your license to use VP8 is terminated. Not sure exactly how that would affect a patent pool, but an interesting battle could be ahead.

Apple adds AirPlay to Mobile Safari

Fri, 28 Jan 2011 00:00:00 -0500

AirPlay is a video feature on iOS devices that lets you play video from your device on your TV, by streaming it to an Apple TV on the same wireless network. Before now this was only available in the iPod and YouTube apps, but with iOS 4.3 (now in beta) it will be available through Mobile Safari as well.

In order to allow AirPlay as an option, video publishers have to add an attribute to the HTML5 video tag. <video width=”480” height=”300” controls x-webkit-airplay=”allow”> … We’ll be adding this as a default attribute in the next VideoJS version.

Read the whole story on MacRumors.

Google is dropping h.264 from Chrome

Tue, 11 Jan 2011 00:00:00 -0500

UPDATE: Added a chart that shows what format support will look like without Chrome supporting h.264.

Google has decided to support the open source community by dropping h.264 support from Chrome. Previously Chrome was the only browser that could play all 3 major HTML5 formats—MP4/h.264, WebM/VP8, and Ogg/Theora. This is probably a strategic move at the same time, since h.264 seems unlikely to be beaten at this point, especially with IE9 supporting h.264 while requiring an extra plugin to use VP8. In my opinion, there’s two major events that could end the format war.

Apple adopts WebM/VP8 (which would require adequate hardware to include in iOS devices)
MPEG LA removes all royalties from h.264

Read the original post.

Over 50% of web users now support HTML5 Video

Fri, 07 Jan 2011 00:00:00 -0500

As we roll into 2011, HTML5 video hits a major milestone. 50.5% of web users now support HTML5 video playback. This number was gathered by comparing browser versions that support HTML5 video with StatCounter’s world-wide browser version statistics. This is a 66% growth in HTML5 video user support since December of 2009. With the expected release of Internet Explorer 9 in the near future, 2011 could see a major increase in websites adopting HTML5 video as their primary playback method. Of browsers that support HTML5 video, Mozilla’s Firefox is the clear leader, with Google’s Chrome in second place. Much of the growth in HTML5 video support can be attributed to Chrome’s success in stealing market share from Internet Explore over the last year.

Video Formats

The format war continues to be a deterrent of HTML5 video adoption, and there’s no clear end in sight. While Apple has helped accelerate HTML5 video by requiring it for video playback on the iPhone, it’s also the one vendor that will not support Google’s WebM/VP8 format, which has the highest potential for becoming the standard format for HTML5 video. Among other reasons, Apple has invested a lot of money in the mp4/h.264 format, including hardware built into iPads and iPhones to decode/encode it. Meaning even if Apple decided to support WebM, it would take more than a simple software update to get WebM to the many iPhone and iPad users. Microsoft has said they will support WebM/VP8 in Internet Explorer 9, however only “when the user has installed a VP8 codec”. Which basically means they won’t support it. Microsoft’s preference for MP4/h.264 was made more obvious with their release of a plugin that allows h.264 to be played back in Firefox on Windows. The following graphs show the support and growth of the different video formats. WebM had a sharp rise in August as Google released Chrome 6 and pushed out updates to its users. In the following charts you can see different views of how formats are divided among HTML5 video users. The first chart shows user support by combinations of formats. The second compares support of open vs. closed formats. From an HTML5 video perspective, open formats win out significantly over closed formats, with Apple and IE9 hanging on to the last 10%. This may change over the next year with the official release of IE9, unless Microsoft decides to support WebM/VP8 without the need for an additional installation. Finally, if you are interested in the Flash vs. HTML5 debate, Flash is well entrenched and HTML5 video still has a long way to catch up. According to Adobe, Flash is supported by over 99% of web users. Statistics from other sites seem to support this, though according to Omniture (now Adobe), the internet average is 116.8% (sic). As of Flash 9 update 3 (9.0.115), Flash has supported the MP4/h.264 format for video playback. In the following chart, you can see how considering Flash affects the comparison of video format support. However, Adobe has said they will support WebM/VP8 in a later release of Flash. The rate that users upgrade to the latest version of Flash is relatively fast, so this could have a big impact on WebM support when it happens. Overall, Flash will be difficult for HTML5 to dethrone. Beyond user support and format discrepancies there is a long list of features that Flash players have supported for years, which will take time for all browsers to build in. However, many of those features can be built with JavaScript, which allows them to be used across browsers immediately. It’s up to the open source community to build the features people need to accept HTML5 as their primary means of video playback. VideoJS is an open source HTML5 video player and framework that makes it easy to support HTML5 video as well as Flash for older browsers. It provides a consistent interface across browsers and solves many browser/mobile device bugs. There are still quite a few rough edges with HTML5 video, but the many contributors to VideoJS are smoothing those over and expanding VideoJS to meet the needs of web users.

HTML5 Video + Google Maps Mashup

Thu, 16 Dec 2010 00:00:00 -0500

Mozilla has a cool demo of playing a video while drawing a line on a Google map similar to what you’d see in an Indiana Jones film. Check out the original post and the demo.

2.0.2 Release - Subtitle Optimization + Safari on Leopard FS Fix

Fri, 10 Dec 2010 00:00:00 -0500

Smallish update with some fixes and optimizations. Rewrote the subtitles parser so it’s a lot more optimized and fixes a subtitle display bug. Put in a check for Safari running on Mac OSX 10.5 (Leopard), which doesn’t like native fullscreen for some reason. Triggering full window mode instead.

Full List

Feature: Rewrote and optimized subtitle code.
Feature: Protecting against volume ranges outside of 1 and 0.
Fix: Bug in Safari for Mac OS 10.5 (Leopard) that was breaking fullscreen.

Download version 2.0.2

2.0.0 Release - Behaviors, fallback APIs, and more.

Mon, 22 Nov 2010 00:00:00 -0500

Big update. The biggest change for current users is a move back to using DIVs for control bar elements instead of unordered lists. There were a lot of conflicting styles issues when using lists, which shouldn’t be an issue with divs. So if you upgrade, don’t forget to upgrade your stylesheets as well.

Beyond that, a lot of code was reorganized and modularized to create a platform for further expansion, like custom plugins and controls. The concept of “behaviors” was added, so you can activate any element on the page to act like a video controls. For instance, the following code snippet will make the specified element act like a play button, and play the video when clicked.

myplayer.activateElement(myElement, "playButton");

The next code snippet will make the element act like a play progress bar, meaning it will grow horizontally as the video plays.

myplayer.activateElement(myElement, "playProgressBar");

Make sites serve you HTML5 video in Safari

Fri, 19 Nov 2010 00:00:00 -0500

John Gruber of Daring Fireball has a cool post on tricking websites to display HTML5 video when they say they can only play Flash. Many sites will tell you they require Flash, even when they actually support HTML5 video for iOS devices.

To add to Gruber’s post, there’s two reasons a site might do this:

They’re trying to protect their content from being easily downloaded, which HTML5 video can’t do very well yet.
They assume everyone with a browser has Flash, and just serve HTML5 video to iOS devices.

So for this first, this is actually a hack to download content some publishers might not want you to. I probably shouldn’t be publishing this since security of the content is one of the main reasons HTML5 video will still take time to spread. But for that purpose, it’s really not hard to figure out.

For the second, it’s kind of lazy implementation of fallbacks. It’s pretty easy to check if Flash is supported, and if not, fall back to HTML5, instead of checking for a specific user agent string. So for sites using VideoJS, this method wouldn’t work, but there also wouldn’t be a need because VideoJS would fallback appropriately to HTML5.

Gruber has disabled Flash in Safari for better performance with video. That says a lot. Most people probably won’t go to same effort he has, but I know he’s not the only one.

1.1.5 Release - Subtitles using track, Android fix & more

Tue, 09 Nov 2010 00:00:00 -0500

Feature: Switched to track method for setting subtitles. Now works like spec.
Feature: Created “players” concept for defining fallbacks and fallback order
Fix: Android playback bug.
Fix: Massive reorganization of code to make easier to navigate

I’ve switched the subtitles to use the new track element defined in the HTML5 spec. You can now add subtitles by creating a track element pointing to your WebSRTsubtitles source.

<video ...>
  <track kind="subtitles" src="../demo-subtitles.srt" srclang="en-US" label="English"></track>
</vide>

The closing track tag is needed, otherwise Safari thinks everything else is a child of the track, even with a self-closing track tag. Not sure why that is, but it’s kind of annoying.

Also a fix for Android playback was added. Android HTML5 video is pretty rough. The canPlayType function returns nothing on Android so VideoJS has a check to see if the source is mp4/m4v, and assumes it’ll play. Then VideoJS adds a click event to the video so it’ll play when you touch it. Also the Android will show the poster image, but no indication that it’s a video and not just an image. Hopefully this will be improved in the next Android version.

Beyond that, I did a massive reorganization of the code, so it should be easier to navigate if you’re planning to hack at it or contribute.

Download version 1.1.5

Version 1.1.4 Release - CSS Loading Spinner & More

Sat, 06 Nov 2010 00:00:00 -0400

The most notable update in this version is a loading indicator (spinner), for when the video is buffering or seeking. The spinner works pretty well, however it’s limited by how accurately each browser tells us what it’s currently doing through triggered events. The spinner works best in Firefox so far. Safari/Chrome are less consistent with what events are triggered and when. For this reason I’m using a more careful approach that makes sure the spinner gets hidden, as opposed to making sure the spinner always shows when the player is busy. There’s a few bugs I had to account for too, like when Safari throws a “waiting” event, but then no other event to let us know it’s not waiting anymore.

The spinner icon is made with CSS3 effects (border-radius and transform). The spinning animation is created with a little javascript for now. In webkit browsers the animation could have been done with CSS3 animation, but I’d rather keep it consistent between browsers. The technique comes from Kilian Valkhof with initial integration into VideoJS by Janez Troha (dz0ny)

Other features and fixes include:

Feature: Added loading spinner.
Feature: Improved styles loaded checking.
Feature: Added volume() function to get and set volume through the player. - Fix: Fix issue where FF would loop video in background when ended.
Fix: Bug in Chrome that shows poster & plays audio if you set currentTime too quickly.
Fix: Bug in Safari where waiting is triggered and shows spinner when not needed
Fix: Updated to show links if only unplayable sources and no Flash.
Fix: Issue where if play button was loaded after play, it wouldn’t hide.

Download version 1.1.4

Version 1.1.3 Release

Tue, 19 Oct 2010 00:00:00 -0400

Version 1.1.3 of VideoJS is now available.

Probably the most notable change is a switch to using a big play button before the movie plays for the first time, as opposed to showing the control bar. The main reason for doing this is actually a bug in Safari. If you try to call any functions on the video other than play, before the video has loaded, Safari will error out. Some people mentioned that fullscreen mode did not work in Safari for them, and this is most likely what was happening for them. This would only happen if you were not preloading the video. You can still go back to showing the controls first through the showControlsAtStart option, but it’s not recommended.

Other features and fixes include:

Feature: Width/Height functions for resizing the player
Feature: Made initial click & hold trigger new value on progress and volume
Feature: Made controls not hide when hovering over them
Fix: Removed trailing comma that was breaking IE7
Fix: Removed some vars from global scope
Fix: Changed a document.onmousemove to an eventListener to prevent conflicts
Fix: Added a unique ID to FlowPlayer demo object to fix a FlowPlayer bug. Thanks @emirpprime.
Fix: Safari error on unloaded video

Let me know if you have any questions.

Video.js Blog

Video.js 4.0 now available!

4.0 Major Feature Summary:

Improved Performance

Greater Stability

New Plugin Interface

New Default Skin

Improved Accessibility

Moved to Apache 2.0 License

100% JavaScript Tool Set

Videojs.com Now Open Source

What now?

Repo Moved!

Site and Support Updates

Brightcove Acquires Zencoder

Version 3.2 Update

3.2.0 / 2012-03-20 / baxter

Version 3.1 Update

3.1.0 / 2012-01-30 / leonardo

Video.js Version 3.0!

Lynda.com HTML5 Video Tutorial Released

How are you using video.js?

New MPEG LA WebM/VP8 Patent Pool

Apple adds AirPlay to Mobile Safari

Google is dropping h.264 from Chrome

Over 50% of web users now support HTML5 Video

Video Formats

HTML5 Video + Google Maps Mashup

2.0.2 Release - Subtitle Optimization + Safari on Leopard FS Fix

2.0.0 Release - Behaviors, fallback APIs, and more.

Make sites serve you HTML5 video in Safari

1.1.5 Release - Subtitles using track, Android fix & more

Version 1.1.4 Release - CSS Loading Spinner & More

Version 1.1.3 Release

2.0.0 Release - Behaviors, fallback APIs, and more.