Alex Reporter
	Description • 14 years ago

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

Bug occurs when viewing a page with active javascript (in my case jQuery) in which the inactive javascript alert, the one which prompts to stop or continue the script, appears. If the user is saving the page, via command-s and the save window is open when the alert takes place, then the application hangs and all menus become inactive.  Waiting does not resolve the issue.  The only option is to force quit or kill-9 the app.

Reproducible: Always

Steps to Reproduce:
1.find or create a page on which the "inactive javascript" prompt will appear after the running script has timed out.
2.load the page and before the alert appears press command-s to open the save page window.
3.leave the app (I used command tab) and do something else, get coffee whatever.
4.when the inactive javascript alert comes up all Fox menus are broken. Neither the alert choices nor the cancel or save choices will work.
5.Fox is now in a locked state and must be force quit or kill-9'd
Actual Results:  
Locked state. Force quit required

Expected Results:  
Either the save menu or the inactive JS alert should have been close-able

I suspect that because both these menus are of the kind which disallow any other interaction until they are resolved, that they interacted in a way in which neither one could be closed.