Summon comment box
Using jun14 builds on Linux rh5.2, NT 4.0 and Mac OS 8.51 When you cancel a news message (and confirm the cancel), the message is not removed from the thread pane. Even if you select another message or group and return, the message appears listed in the thread pane. Even exiting and returning doesn't do it. Another issue (which may be part of bug #7778) is that the contents of the message pane are not cleared until you make another selection then return to the cancelled posting, at which time you'll see the "bad article" error message in the message pane. 1. Launch messenger using prefs specifying news server & group. I had one server specified, news.mozilla.org and used netscape.test 2. Open netscape.test, select a message you posted. Edit|Delete Message. Result: message still appears in thread pane and the message contents still display in message pane. Select another message and find the cancelled message is still displayed in the thread pane. It should not be. Message header still displays even after exit.
moving to m8.
would not hold m8 for this.
still not there yet. slipping to m10.
Sounds like this needs to be fixed for PR1, so I added a note in the Status Whiteboard
Triage to M11
Triage to M15
Change QA Contact to me.
*** Bug 14717 has been marked as a duplicate of this bug. ***
Linux 12-17-10-M12: By the way, there is a error message pop up: "A New (NNTP) error occured: No such article" This error should be disappear with the newsgroup message as well.....
Release Notes for M12.
Release Notes for M13.
turning [PR1] into beta1.
Putting on PDT- radar for beta1.
Yes. Problem still occurring on 03-07-08/09-M15 commercial builds.....
moving to m16.
Mass moving M16 to M17 - look for nsbeta2 before anything else.
fixed.
Verified on all the platforms: WinNT 4.0 : 05-24-09-M16 commercial build Mac 9.0.4 : 05-24-08-M16 commercial build Linux rh 6.0: 05-24-08-M16 commercial build After delete message will cancel news message from the thread pane now. Updating the keywords from beta1 PDT- to nsbeta2 & Marking as verified!!
Linux (2000-07-31-04 M17) Actual result: After the message is cancelled(delelted message). Exit and relaunch. The deleted message still shows in the thread pane. click on it, message pane is blank. Expected result: Message should not show up in the thread pane once it is deleted. Reopen this bug.
I'm using today's linux m17 build and I didn't have a problem -- cancelled message doesn't return. No problem for me.
Spoke with lchiang and triage team. Will not hold beta2 for this. Putting on [nsbeta2-] radar.
I think I got results for passed & failed depanding on whether I am using migrated profile or not: 1) If I am using a migrated profile -- it will pass, the cancel messages will be removed from the thread pane within the same session without exit. 2) if I am using a new profile -- it will fail, the cancel messages will NOT be removed from the thread pane within the same session even exit and relaunch again. If this will be nsbeta2-, I will suggest to release note for this problem. Ccing David (since Seth is out), do you know why this problem is ONLY occurring on new profile? Adding new profile on the summary to specify this problem!!
Linux (2000-08-01-04 M17) Same result as Kanren Migrated profile: passed New profile: failed
For M18 builds, please see bug 47236
Clear nsbeta2- & nsbeta2 since beta2 is over. Adding nsbeta3, regression for the keywords.
This is still occurring on the current build. Since it will misleading users thinking that the cancel messages haven't been removed, so I am removing the nsbeta3- to renominate this bug again.
nsbeta3-. We originally gave this a minus because the cancel actually works, because we think most news users will be migrators and won't hit it. In addition, it meet the current P1 or P2 criteria of data loss, crash, major feature failure.
accepting.
mass change of huang's news bugs to stephend.
is this still happening? I thought navin fixed this. cc'ing naving.
I didn't see it happen using dec13 commercial trunk builds (I tried with win98 and mac OS 9.0, assume linux is same). Will close as worksforme. There may be some weird cases where it may still happen, but in the straightforward cases, it appears to be working. If we find any problem case, Stephen can log a new bug.
By the way, I tried on both new profiles and migrated ones.
or
