We receive a lot of questions from customers about HTML5. Most people who deal with video regularly in their business have heard that HTML5 supports a simple <video> tag. Simply drop that tag into your page, and you’ve got a full-fledged video player, ready to go and able to be played on every modern web browser out there.
Well, that’s not quite the case. The <video> tag, and HTML5 as a whole, was created by standards committee. And, just like every standards committee, multiple political and organizational forces push development of those standards in many directions. Video in the browser is particularly subject to this: many popular video and audio codecs are patent-encumbered, and many of the major players who create browsers are patent holders.
|Theora video, Vorbis audio, Ogg container||-||3.5+||*||5.0+||10.5+||-||-|
|H.264 video, AAC audio, MP4 container||-||-||3.0+||5.0–? **||-||3.0+||2.0+|
|* Safari will play anything that QuickTime can play. QuickTime comes pre-installed with H.264/AAC/MP4 support. Extending QuickTime to support Theora and WebM requires users install plugins, which few are likely to do.|
|** Google Chrome will soon drop support for H.264.|
Clearly, this is a complicated landscape that will require another 5-10 years to clear up and standardize. Furthermore, HTML5 has limited to no support for what an even basic native or Flash-based player will get you:
- Events that fire on active (play, pause, etc.) and passive (video complete) events
- Ability to determine location in video file for bookmarking and experience tracking
- Adaptive bitrate switching (outside of, perhaps, HTTP Live Streaming (HLS) on Safari and iPhone)