Using 1999051809 Linux Using 1999051808 NT 4.0 Using 1999051709 Mac OS 8.51 (slightly different results for Mac) Mark message read or unread doesn't work after sorting thread pane or using View Unread. This is true on single or multiple message selections. 1. Launch apprunner, go to messenger window. 2. Open a folder having several messages. 3. Select a message. Mark it unread and read a couple times to demonstrate that both marking read and unread do indeed work. Mark a couple other messages to demonstrate marking other messages will work. 4. Sort the thread pane by subject. 5. Select another message. Mark it unread. RESULT: mark message doesn't do anything Note: In the above scenario the mark message will indeed work if you do not change message selection after sort. Note2: This also applies when trying to mark messages in View|Messages|Unread.

Oh, forgot to mention I was using simple profile, one POP account.

Changing to M7. Chris Waterson is working on an optimization Bug 6665 which may make this problem go away.

I'm going to change the title of this bug if that's ok. Right now, if you sort, operations on messages will possibly not work. This includes deleting, copying, and marking messages read, plus any other operation that depend on nsMsgHdr's. The comment I wrote about Bug 6665 making this work still holds true.

I'm going to change the title of this bug if that's ok. Right now, if you sort, operations on messages will possibly not work. This includes deleting, copying, and marking messages read, plus any other operation that depend on nsMsgHdr's. The comment I wrote about Bug 6665 making this work still holds true.

I'll put this towards the M6 release notes.

Add to this the fact that once you sort, sorting again doesn't work. See 4731 for more discussion of where this fails.

Reassigning this to M8. Sorry that all of these bugs will exist for another few weeks at least. Note that if waterson fixes 6665, then this bug should go away, at least to the user. However, the underlying problem will still exist so I don't want to mark this bug as dependent on that fix. The problem is due to the fact that given a message uri, we don't know how to create a message. There's a possible rearchitecture that will happen eventually (maybe M8) that wil address this.

Chris fixed it so these problems go away. However, I still don't know how to fill in an empty nsIMessage unless I create it myself. As far as I know there's nothing in the product that's currently depending on this, but there might be one day. I'm marking this as M9.

Fenella - you can go ahead and verify the fixes made for the originally reported steps. But, leave the bug open (don't mark it fixed) since Scott is using this to track something else.

Linux (1999-06-30-08 m8) Win32 (1999-07-01-08 m8) Mac (1999-007-01-08 M8) Using the original steps as mentioned on 5/18/99, I try it on all three platforms, the problem no longer exists.

I'm pushing this off again. I still need to do this, but it's probably becoming less important as long as sorting still works.

Moving to M15.

Adding perf keyword

This is not a performance bug! Removing perf keyword.

Move to future target milestone for review in a later release.

I do not believe this bug is valid anymore given the change to outliner. cc'ing sspitzer in case I'm wrong. Marking invalid.

marking verified -- old invalid or wontfix resolutions