Closed Bug 201609 Opened 23 years ago Closed 23 years ago

Cancelling publish doesn't really cancel currently executing uploads

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jag+mozilla, Assigned: jag+mozilla)

References

Details

(Whiteboard: [adt2])

Attachments

(1 file, 1 obsolete file)

In testing for another bug I found that calling cancel while we're publising a document doesn't really cancel it, the upload keeps going till it's done or Mozilla gets closed (whichever happens first). There seem to be two problems. One is that in the JS for the dialog we don't have access to the webbrowserpersist object to call cancel on it, the other is that with that fixed (patch coming up) the backend still doesn't cancel any channels open for this (these) upload(s).
See bug 201610 for the backend problem.
Comment on attachment 120175 [details] [diff] [review] Alternate approach, return the persist obj from StartPublishing r=ssu
Attachment #120175 - Flags: review+
Attachment #120171 - Attachment is obsolete: true
Attachment #120175 - Flags: superreview+
moa=brade
Checked the patch in, waiting for bug 201610 to be fixed.
Depends on: 201610
Editor triage team: nsbeta1+/adt2 Marking fixed since jag fixed the front-end issue and has filed 201610 for the back-end issue.
Status: NEW → RESOLVED
Closed: 23 years ago
Keywords: nsbeta1nsbeta1+
Resolution: --- → FIXED
Whiteboard: [adt2]
I'm not sure how to verify this one since bug 201610 hasn't been resolved yet.
From my testing with the 2003-05-23-09 Win32 and 2003-05-23-07 Macho trunk builds, I was able to successfully cancel the ftp publishing process in Composer.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: