568530 - Javascript failure popup bigger than the screen

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Fadil Eldin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9

It happens to me in authentication to BlueHost through CPanel.
When the session expires, the failure of authentication causes a javascript failure popup to appear with a long javascript code.
Since the code is very large, it goes above and below the screen, and covers about 50% of the width of the screen. the "close" button is not visible or reachable.
You can not scroll down or up to find the "close" button and click it to make the popup disapear, at the same time FireFox and all its open tabs are not clickable.
The only solution to recover from the problem is to kill firefox from windows task manager.


Reproducible: Always

Steps to Reproduce:
1.login to CPanel
2.wait long enough for the authentication to expire
3.click any link on cpanel

This is just an exmpale, I think every large javascript code causes the same problem


Expected Results:  
see portion of the javascript if the whole thing takes more than one screen, and the ability to page next and previous on large javascript code on popup screens.

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.