It's fixed now. It was just a slight HTML error that didn't really effect Gecko or Webkit browsers but IE decided to handle it terribly and bork every single link that appeared after the HTML error. It's all sorted now though.
Most of you (including me) wouldn't have noticed as you would have probably been using Chrome, Safari, Opera or Firefox.
@Hermit: That's odd. I guess it could be that it affected older versions of Chrome. Do you have auto-update enabled? Also, I'm signed up to receive developer/nightly builds so it's possible that we weren't using the exact same version of Chrome. Still, with Chrome using the Webkit rendering engine, I'm surprised you had any problems at all.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.