I can reproduce your problem on Firefox 16.0.2 , and this is fixed, at least on our Nightly builds, perhaps before that. But it is certainly embarrassing and should not happen (and was not caught during our extensive testing and beta phases), I'll look into back porting the relevant patches.

Again, sorry about that.