I experienced this issue myself on IE7. I restarted the browser and the problem disappeared. In the very limited beta rollout (5 users), the one that uses IE and not FF called to complain about this very issue. It is clear that there is a bug.

Now we just need to figure out how to reproduce it.