I discovered this issue and fix independently a couple of weeks ago and I can confirm this fix works.

It’s no longer an issue here though on Chrome 23. Might be a Chrome 22 bug that was fixed maybe?