That’s a confirmed Google Chrome bug, Derek. Other webkit-based browsers are fine.

I’m confident the Chrome team will get to the bottom of it soon.