Closed Bug 17061 Opened 25 years ago Closed 24 years ago

unknown-content-type dialog is being thrown even when a url load fails

Categories

(SeaMonkey :: General, defect, P2)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jud, Assigned: law)

Details

steps to reproduce: Goto: ftp://ftp.boulderdesign.com and when it asks you for auth info, hit cancel. This causes FTP to fire OnStopRequest() out to the docLoader w/ a failure status code and error msg. That should be sufficient to prevent the save as dailog from being opened.
Summary: unknown-content-type dialog is being thrown even when a url load fails → [DOGFOOD] unknown-content-type dialog is being thrown even when a url load fails
Summary: [DOGFOOD] unknown-content-type dialog is being thrown even when a url load fails → unknown-content-type dialog is being thrown even when a url load fails
Changed my mind; mozilla would taste fine without this being fixed.
morse, my fix for 17521 is independent of this.
Status: NEW → ASSIGNED
This seems like a bit of a nasty problem. We first get the OnStartRequest (which triggers the unknown-content dialog), followed by the OnStopRequest. The latter comes too late to stop the dialog. On the face of it, I can't see how to discern any status from inside OnStartRequest. I think the fix should look something like: if ( channel->Status() == OK ) { // Do HandleUnknownContent stuff now. } I'm adding rpotts to cc: list 'cause if anybody knows, it would be him. Rick?
AsyncOpen will fix this.
Target Milestone: M13
Priority: P3 → P2
Target Milestone: M13 → M15
Not required for beta 1.
Moving all UE/UI bugs to new component: User Interface: Design Feedback UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback
Move to M16 for now ...
Target Milestone: M15 → M16
Target Milestone: M16 → M18
Move to M21 target milestone.
Target Milestone: M18 → M21
I don't think this is a problem any more. Unfortunately, boulderdesign.com seems to have redone their ftp authorization process so I can't reproduce. If another site demonstrates the problem in the future, we'll deal with it.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Chaning the qa contact on these bugs to me. MPT will be moving to the owner of this component shortly. I would like to thank him for all his hard work as he moves roles in mozilla.org...Yada, Yada, Yada...
QA Contact: claudius → zach
Component: User Interface Design → Browser-General
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.