Will Beattie's Blog

  I just received a bug report about the infamous Internet Explorer Security Warning for one of the pages in our application that serves video content over HTTPS.   After viewing the source I found the offender which turned out to be the codebase attribute set to http://www.apple.com/qtactivex/qtplugin.cab . < object id ="videoObject" classid ="clsid:02BF25D5-8C17-4B23-BC80-D3488ABDDC6B" codebase ="http://www.apple.com/qtactivex/qtplugin.cab" width ="330" height ="292"> < param name ="src" value ="https://securedomain/video.mp4" /> < param name ="controller" value ="true" /> < param name ="autoplay" value ="False" /> < param name ="scale" value ="aspect" /> < param name ="cache" value ="true"/> ...

  Recently there was a question asked over on Stackoverflow.com regarding best practices around H.264 and the Video Tag. The answer with the most votes has IMO provided an inadequate solution and I thought I would take the time to clear this up with a new post. Unfortunately and to the frustration of developers that deal with Video content, HTML 5 has dropped the Codec as part of the specification leaving the Browser vendors to implement whatever they want. However the consensus is to use H.264 with even Microsoft adopting this for the forthcoming Internet Explorer 9. Here’s how it stacks in terms of browser support as of writing. Browser H.264 Ogg Theora Google Chrome Yes Yes Firefox No Yes Safari Yes No IE9 Yes No Opera No Yes H.264 Only – Chrome, Safari ...