Bunfightclub: HTML5 Video – Google Vs. H.264

Allow me to digress. I know, I’ve not even started yet, but hey, what do I care?

I got an update from JW Player today that prompted me to check out their player again. I’ve recently been implementing open source HTML5 video solutions, and as a former proponent of the once world conquering JW Player, I thought I’d check out their latest offering.

Indeed, they are up to speed, as you would expect, and open source. But, licensing is STILL required for ANY ‘commercial’ (i.e. pretty much ANY full stop) website. Oh well. Sorry guys, you had a dominant position and probably make a lot of money these days, so drop those prices and create a more liberal definition of commercial and I’ll consider recommending you again. In the meantime I look forward to seeing you taken down a peg or two.

Forward the properly open standards!
For more on the subject, and some solutions I’ve tried, see my earlier post Fully cross platform video – HTML5 for iPad/iPhone with Flash fallback for older browsers


A blog on their site brought something to my attention however – Google have dropped H.264 support from Chrome. This is a bit of a bunfight over standards, and has also stirred up a bunfight amongst commentators.

This blog on TechCrunch lays right in to Google over it, (as do a lot of commenters on the Chromium Blog post above) and they also dig at them over their proposed WEBM plugins for IE and Safari.

Personally, I understand Googles decision, and side with the Opera developer/blogger Havaard who explains his reasons for supporting Google’s move and also clarifies some of Googles arguments rather well. 

Gavick Pro ‘GK Gamebox’ Joomla Template – popup login disappears when clicking on username or password input in Chrome


In Google Chrome, when using the popup login form accessed from the login link at the top of the template, if you click on the username or password inputs, the popup disappears.


The mootools script is designed so that when a user clicks out of the DOM object popup_login, it fades out. This is done with any general document click IF the mouse is out of popup_login. This is determined by checking a variable set by mouseenter and mouseleave.

In Chrome, mouseleave is triggered when you enter child elements – not our desired functionality!



130a131> <span style="white-space: pre;"> </span>$('popup_login').getElements('input').addEvent('mouseenter',function(){login_over = true;});

(Unix diff formatting)