Thanks for the feedback! I believe that was a Chrome specific issue which I did not expect. It should be fixed now!
