Indeed, thanks for reporting this. I've found and fixed the issue -- it was a weird one where it worked fine in some browsers and not others. You don't see too many of those these days, thankfully!
The fix should go out in our next deploy, which will be tomorrow morning London time.