We are working on this issue. It seems to be related to use of the Mozilla Firefox browser, you should not experience this with Google Chrome so please try that for now while we resolve the underlying issue. Thanks.