Hi,
That was a browser compatibility issue. It has now been resolved.
Thanks for bringing it to our attention.