Closed
Bug 180384
Opened 22 years ago
Closed 22 years ago
nsExternalHelperAppService should observe profile changes
Categories
(Core Graveyard :: File Handling, defect)
Core Graveyard
File Handling
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bzbarsky, Assigned: timeless)
References
Details
Attachments
(1 file, 1 obsolete file)
5.95 KB,
patch
|
ccarlen
:
review+
dmosedale
:
superreview+
|
Details | Diff | Splinter Review |
This is because we need to change to the new mimeTypes.rdf, mmkay?
Blocks: profile-switching
i'm going away for a bit, but i figured i'd put something up so that people
would have it if they needed it. i haven't applied the profile change patch so
this is mostly untested, but it compiles and i think the program flow is
correct.
Comment 2•22 years ago
|
||
I have the patch for bug 97622 in my tree, tested this, and it works.
One thing though:
- // we must be shutting down xpcom so remove our temporary files...
- ExpungeTemporaryFiles();
This now happens in response to the profile shutting down, not XPCOM shutting
down. If that's the case, why is this observing XPCOM shutdown anyway - just to
remove itself as an observer? I think it's better just to use ownsWeak==PR_TRUE
with the observer service.
Comment 3•22 years ago
|
||
Should we mark this one with patch keyword?
![]() |
Reporter | |
Comment 4•22 years ago
|
||
There is no such keyword.
Attachment #109117 -
Attachment is obsolete: true
Comment 6•22 years ago
|
||
Comment on attachment 112250 [details] [diff] [review]
weak ref + handle failures
r=ccarlen. Fix this comment, though:
+ /* Add an observer for XPCOM shutdown and profile change*/
Attachment #112250 -
Flags: review+
Attachment #112250 -
Flags: superreview?(dmose)
Comment 7•22 years ago
|
||
Comment on attachment 112250 [details] [diff] [review]
weak ref + handle failures
sr=dmose
Attachment #112250 -
Flags: superreview?(dmose) → superreview+
checked in
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•