Thanks for pointing this out, this was reported by a few others. We are investigating it. For now, just refresh the page and it should work.