Hey @unity4625
After some troubleshooting, this seems to be a bug in the recent version of Chrome. We’ve just created a new topic with a couple of solutions
Let us know if that solves this for you!