Thanks for the heads up. I blame our site's Chief CSS Officer (me). It has been fixed!