Still diagnosing. There was a line of code that we are 100% sure caused this. We removed the code, but the complication might be if some users still have a cookie from that provider which was causing some javascript conflicts.
Either way, there are additional steps we are taking...
In the mean time, if you haven't cleared cookies and logged out/logged in, please do so as that should correct it.