Closed Bug 8101 Opened 21 years ago Closed 21 years ago

[PP]Profile Manager [exit] button takes to apprunner

Categories

(Core Graveyard :: Profile: BackEnd, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: agracebush, Assigned: racham)

References

Details

Profile Manager shows two buttons, [exit] and [start communicator]. They both do
the same thing.  When I pressed [exit] I expected to return to console ie exit
the Profile Manager

(build 1999061308)
Status: NEW → ASSIGNED
Target Milestone: M8
We need to identify a way exit the whole app in a sane state on clicking the
'Exit' button. Moving the TFV to M8.
This isn't critical and it isn't done - moving to M9.
Target Milestone: M8 → M9
Target Milestone: M9 → M10
Moving TFV to M10. Including Ramiro onthe cc list for general consultation.

Ramiro, Is there an API that you are aware of which when called quits the whole
app not just the (toplevel)window in which it happened..?
P3s aren't going to make it in M10.  Bulk moving to M11.
Blocks: 12696
These bugs are not critical for beta 1, moving out.
adding myself to the cc list.
No longer blocks: 12696
Target Milestone: M15 → M12
Failing to exit the app is causing mail to crash.  Need this in the beta.
*** Bug 13167 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Exit now exists the whole application. On hitting Exit, the javascript calls the
interface that makes the file profile services to forget about the current
profile. The in the profile code, we check to see if there is a current profile,
if there is no current profile, we quit the whole application. Part of Seth's
fixes. Marking fixed.
Status: RESOLVED → VERIFIED
this has been working for a while now, verified in build 1999101208
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.