Open
Bug 289221
Opened 19 years ago
Updated 2 years ago
Make nsExternalHelperAppService an nsIProgressEventSink
Categories
(Firefox :: File Handling, enhancement)
Firefox
File Handling
Tracking
()
NEW
People
(Reporter: Biesinger, Unassigned)
Details
currently, exthandler gets the progressMax value manually from the content length... it would be nice if it could be an nsIProgressEventSink. That likely needs changes in uriloader. See also bug 228968 comment 124 and the next one.
Comment 1•19 years ago
|
||
Doesn't exthandler put the request in its own loadgroup? Shouldn't changing loadgrourps change where progress events go to, maybe? That is, can't we just observe progress on our loadgroup?
Reporter | ||
Comment 2•19 years ago
|
||
actually it sets the loadgroup to null these days. you can't set notificationCallbacks after a channel has been opened currently... and setting the loadgroup does not affect that either.
Updated•15 years ago
|
Assignee: file-handling → nobody
QA Contact: ian → file-handling
Updated•8 years ago
|
Product: Core → Firefox
Version: Trunk → unspecified
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•