Closed
Bug 241506
Opened 21 years ago
Closed 21 years ago
onStatusChange in nsProgressDialog should do nothing
Categories
(Core Graveyard :: File Handling, defect)
Core Graveyard
File Handling
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Biesinger, Unassigned)
Details
so, as it is, this shows an error dialog when aStatus is not a success code.
But, when this is called, the notifications are coming from webbrowserpersist,
which gets them through nsIProgressEventSink::OnStatus.
now, a real error will not be notified this way. in fact, that's handled
elsewhere already.
this code should just be not there.
but, it also exists in nsProgressDialog; and firefox of course duplicated this
code into two (!?) helper app dialog impls
![]() |
||
Comment 1•21 years ago
|
||
So a problem is that nsIWebProgressListener claims a nsresult status; should it
really claim some other type?
If not, it should very clearly document what that status means.
I guess we should file some bugs on firefox too.
Reporter | ||
Comment 2•21 years ago
|
||
nevermind, this is also called from nsExternalAppHandler::SendStatusChange, and
it is very definitely an error there.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
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
•