Closed
Bug 53107
Opened 24 years ago
Closed 24 years ago
Mozilla is crippled after returning from the background with no windows
Categories
(Core Graveyard :: Widget: Mac, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: scc, Assigned: saari)
Details
If you close all content windows (i.e., log window doesn't matter) in Mozilla and then bring some other application to the front; then when you next bring Mozilla to the front, you will no longer be able to make any new windows nor quit the application. Didn't really know who should own this bug; took a guess. Re-assign and don't hate me if I'm wrong, Dan :-)
Reporter | ||
Comment 1•24 years ago
|
||
...and the winner is: Chris Saari. re-assigning to saari at his request after a short discussion on #mozilla
Assignee: danm → saari
Comment 2•24 years ago
|
||
wfm using moz verification build on 8.6
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 3•24 years ago
|
||
if scc meant that cmd-keys didn't work when there were no windows, then yes, this was fixed yesterday by danm's checkin. if even selecting things from menus manually was the problem, then i have no idea.
Reporter | ||
Comment 4•24 years ago
|
||
I actually had to quit using Macsbug. Command-Keys didn't work; but neither did selecting menu items with the mouse. I relaunched and tested multiple times to determine the exact minimal sequence needed to reproduce. It was 100% reproducible on my buiild of the 18th. Hope this helps, Mike.
Comment 5•24 years ago
|
||
scc, there are problems with menus being ignored with no windows if you activate the console window. obviously, it's debug only, so it's not and end-user problem. btw, if the console window is active, you can cmd-. to quit the app. just a shortcut.... leaving WFM.
You need to log in
before you can comment on or make changes to this bug.
Description
•