Got the same issue: this bug is really weird. Working perfectly fine in Firefox but Chrome decided to mess it up for some reasons.
It's with the latest version of Google Chrome. If you downgrade it works again. But since Google doesn't want you to downgrade...

A friend of mine got the issue too, so it seems like the bug occurs pretty frequently. Hopefully Sindre can try to fix it with the upcoming 5.3 beta builds.
