Need progress notification from back-end for sending message. This is neccessary to provide the front end progress dialog while sending a message.

nominating for nsbeta1

FYI, the frontend bug is bug 28348

marking nsbeta1+ and moving to mozilla0.8

change qa contact to myself and cc - esther

The fix for 32222 depends on a necko branch landing which isn't going to happen for mozilla .8. So this won't be done till .9. Moving the target milestone.

moving to 0.9.1

I still have a few minutes worth of polish left to finish this up but here's the bulk of the changes....

Scott, any ETA when you plane to finish it?

changing TM to 0.9.2 per PDT meeting (you can check the fix into 0.9.1 trunk until Friday, 18/May/01 or after the 0.9.2 is open)

moving to 0.9.3. Please hold onto the fix in case we can get this in later.

Adding nsbranch. I think we should try this one on the trunk first.

I just resurrected this patch and brought it up to the tip. I also added text to the right of the progress bar to show the progress in terms of a percentage. Note the small localization change I'll need to get approval for as well.

please ignore the changes to nsMsgComposeProgress.cpp in the patch. That file is obsolete and not part of the build. Those changes won't get checked in. I also took out an errant dump statment I had added to MsgComposeCommands.js

don't bother updating nsMsgComposeProgress.cpp & nsMsgComposeProgress.h , those files are not used anymore and should be removed. R=ducarroz

sr=sspitzer

This has been checked into the trunk Adding the vtrunk keyword. Now waiting to make it into a limbo build.

I saw one minor bug, and that was when I attached a super large BMW Film Player on my Mac, the "Status:" area said "Attaching #1%". As soon as it was attached though, it began to send fine, after which it copied. Not sure what the hash symbol is doing in there (seems minor though). The actual sending was fine, as was the progress meter during which it gave a "Progress: X%", after which it told me that it was copying to the Sent folder. Verified fixed (*TRUNK*): Windows 2K : 2001-06-29-04 RedHat 7.1 : 2001-06-29-06 Mac OS 9.1 : 2001-06-29-05

stephend, can you log new bugs on those problems? they both sound like valid problems for mscott.

Please don't log new bugs for those. I already checked in a fix under this bug the other day. Thanks.

Trunk builds: 2001070206-win98, 2001070205 mac NOTE: I am having problems with linux builds. Using above builds I see the % progress notification while sending message. Now it acutally shows the %progress while sending message. I also did not see any #1% in the status area. So this has been fixed too. According to this bug which is about the send progress has been verified only on trunk build. However, I noticed a few things that I have listed below. I know this is still being implemented. Scott if you think I should log new bugs for the ones below let me know. 1.when attaching a small file and sending message the completion of send progress could be anywhere in between and does not always show 100% before the compose window disappears. I saw that the progress % at 66% and then the compose window disappeared. But the message was received fine. 2.when copying message to sent folder locally and with pop account I did not see the copying to sent folder progress come up. It shows only the send progress 100% and the just appears to be frozen while copying message to the sent folder. The spinning progress in the status bar of the compose window also stops after the send progress reaches 100%

trunkverified for original problem

Scott or Jean-Francois, what would it take to get the copying to sent folder back in?

I don't know what you mean by "copying to sent folder" back in?

Sheela's point #2, I think I used to see a progress message that said "copying to Sent folder" which I don't think I'm seeing anymore. Now that we're not going to get this on the branch, we can probably mark this fixed and open up new bugs for any new bugs that come up.

since this is no longer going into the branch this bug is fixed.

There are two new bugs logged as per my comments on 2001-07-03 14:56 - Bug 94788, bug 93465 verified 2001-08-10-08 linux 2001-08-10-09 mac 2001-08-09-09 win98