Thanks for your feedback! We realized this bug on Chrome, we're trying to fix it now. I'll let you know when it's fixed.
