I noticed the same thing while on the site at that time - but closing down the browser and logging back on seemed to solve it.