We have a fix for this which we'll release in an upcoming deploy.

---

We've heard about this from a couple of folks now and are investigating. Thanks for the feedback.