I've done some testing and I can also replicate this in Chrome. I spoke to the forum software developers and they insisted it's a bug with Chrome, rather than their software - so I think we may have to wait this one out for a week or two and hope it's fixed in the next release.
I really appreciate the heads up on this, I hadn't spotted it until you mentioned it.