I can confirm, the bug is in chrome as well.
Huh, that's very surprising. Whatever it is, it has completely eluded all developers and testers. We've tried all OS+browser combinations available to us, but haven't been able to replicate it. If you see it again, I'd really appreciate if you can share a screenshot of the browser console and version!