Closed Bug 265562 Opened 20 years ago Closed 20 years ago

pop up dialog messages won't close

Categories

(Firefox :: Toolbars and Customization, defect)

PowerPC
macOS
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 232715

People

(Reporter: lists, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

After using the browser for a while (usually in the range of few hours) any new
dialog boxes that firefox opens will not respond to "Close" or "Cancel" buttons.
 The most recent example of this was a "Could not load the requested page"
dialog.  When this happens it maintains focus on the dialog, and with no way to
close the dialog the only option is to close the whole application. 
I've also noticed that the loading status bar will sometimes stay in the fully
loaded blue position, and the bookmark nav bar will not be drawn on new loads.
This seems to happen after I have opened up a few windows and opened a group of
bookmarks in tabs.  

Reproducible: Sometimes
Steps to Reproduce:
1.Open multiple firefox browser windows
2."Open in Tabs..." a directory of bookmarks in each browser window
3.open a dialog box  (have noticed with a "Resouce does not exist" dialog, and
the customize the navigation bar dialog.

Actual Results:  
The dialog window will not respond to close or cancel button presses and stays
open.  If this dialog holds focus the application is rendered useless and must
be fully shut down. 

Expected Results:  
dialog should have closed as expected to continue work.
That was probably after a disk sleep and it is fixed in the latest nightly
builds, you can grep one from:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-0.9/



*** This bug has been marked as a duplicate of 232715 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
QA Contact: bugzilla → toolbars
You need to log in before you can comment on or make changes to this bug.