We have identified the problem, which appears to be caused by Chrome on macOS. We will fix this issue with a patch in the next version.
Can you give me the code to patch it on my local meanwhile
We will release the next version soon; please wait patiently. And we recommend that you use Firefox or other browser before then.
tested today with version 1.10, same problem