Closed Bug 233145 Opened 21 years ago Closed 21 years ago

stop implementing nsIURIContentListener in nsExternalAppHandler

Categories

(Core Graveyard :: File Handling, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.7alpha

People

(Reporter: Biesinger, Assigned: Biesinger)

References

Details

Attachments

(1 file)

there is no real reason for this. RetargetLoadNotifications can just set
loadgroup and notificationCallbacks to nsnull.
this also makes nsIINterfaceRequestor unnecessary
Attachment #140663 - Flags: review?(bzbarsky)
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.7alpha
Comment on attachment 140663 [details] [diff] [review]
patch

>Index: nsExternalHelperAppService.cpp
>-  // make our docloader release the progress listener from the progress window...
>-  if (mLoadCookie && mWebProgressListener) 

and so on.  This part bothers me -- I have no idea what it does and why (and
more importantly whether not doing it leaks).

Other than this one caveat, this looks great.
bz: nothing calls closeProgressWindow. Changing this function does therefore not
affect any possible leaks.

I have no idea why that function exists, too...
Comment on attachment 140663 [details] [diff] [review]
patch

r=bzbarsky
Attachment #140663 - Flags: review?(bzbarsky) → review+
Attachment #140663 - Flags: superreview?(darin)
Comment on attachment 140663 [details] [diff] [review]
patch

sr=darin
Attachment #140663 - Flags: superreview?(darin) → superreview+
checked in
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Depends on: 341806
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: