In reply to Bottom Clinger:
It still looks like just a cache issue, but not sure why its so persistent
It may be worth clearing your browser cache.
Should only be affecting threads you opened in the short window the bug was live yesterday morning.
I'm presuming it works for you on a different browser?