This is a known issue with Chrome 34.0.1847.116 and will be fixed in the next release....
Yes! Please move to github!