We've confirmed that this issue started happening with Chrome update 27.0.1453, which was launched yesterday, May 22, 2013. We can confirm that this issue does not occur on the prior version of Chrome (26.0.1410). We are investigating.