Closed Bug 267097 Opened 20 years ago Closed 7 years ago

unable to close the application in mac os x when webpage is loaded

Categories

(Firefox :: Shell Integration, defect)

1.0 Branch
PowerPC
macOS
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cameron.e.wood, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

When trying to close the application via the dock icon or the apple menu bar it
does not close the application... it seems to only close the application once
you have closed all open windows first. 

Reproducible: Always
Steps to Reproduce:
1. Start the browser
2. Then open a website, other than your homepage
3. Now attempt to close the application via the dock icon or apple menu

Actual Results:  
Nothing! The application ceased to close as expected.

Expected Results:  
It should have closed the application regardless of any windows that were open!
*** Bug 267887 has been marked as a duplicate of this bug. ***
(In reply to comment #0)

Just wanted to note that this problem still persists in Firefox 1.0, however it
is now somewhat random, sometimes it works and sometimes not! I have tried to
notice some kind of pattern to this behaviour but i cant see any :(
Severity: normal → major
Version: unspecified → 1.0 Branch
Confirmed: We are experiencing the same issue.
Firefox 1.0
MacOSX 10.3.6
on both: PowerBook G3 400 and iMac G4 1GHz (for what it's worth)
If a Firefox window is open at all (regardless of whether a site is loaded or
not), Firefox will not respond to the Quit command.  Once the window is closed,
Firefox will respond and shut down as it should.  It's not a show-stopper of a
bug, but it is definitely an annoyance.
This seems to work fine in FF 1.5.
Assignee: bugs → nobody
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.