I think it may be likely that users who are updating from the 2.0.3.3 beta and also using Chrome will encounter Chrome: Empty status bar starting with 2.0.3.5. The posted solution to that (which also worked for me) was to clear Chrome’s browser cache.