Bug 331159 ended up regressing Bug 220173. If you are reading a message that has scrollbars in the message pane, and the folder gets new mail that gets marked as junk, we end up re-loading the message you are reading, causing the scrollbars to jump back to the top.

David, did you end up fixing this in the back end recently? I seem to remember reviewing a change that might have fixed this regression from 331159 as well.

I think this is still an issue.

I can additionally confirm this behaviour on Max OSX (10.3) with Thunderbird version 2 beta 2 (20070116). Scrolls to top of message when Junk mail is processed after get mail, but not when a normal message is received.

I'll look into this.

Is the mail just marked as junk, or does it also get moved to the junk folder? Is it marked as junk by the bayesian junk filter, or a normal filter?

Hey David, the mail you are reading isn't getting marked as junk, but the front end gets the notification when the junk filter processes incoming messsages other than the one you are reading and it can't tell that it wasn't this message so it tries to reload it, thinking the junk state has changed. see comment 0 and the hacky work around we used to have in Bug 220173 to prevent the message from getting reloaded.

This seems to be working for me in imap and pop3 accounts. I turned off my mail filters, and my ab whitelisting. Then, I selected an html message which I then scrolled a couple pages using the space bar. Then, I got some new mail, which was analyzed for junk status (neither were junk). I didn't see any scrolling. Should I mark the current message as junk so that it thinks the junk status has changed because the incoming messages(s) aren't junk?

I see it when new mail comes in and gets marked as junk while I'm reading a non junk message.

Seeing this as well on pop3... uber annoying.

ah, so a new incoming message needs to get marked as junk for this to happen...I'll try that.

this seems to be working for me...I tried marking a message as non-junk and it was reloaded...

Comment on attachment 254837 [details] [diff] [review] use new mechanism to find out if junk bar state has changed ooh way to use the new isFlagSet stuff. I think you can use kMsgNotificationJunkBar instead of 2 for the argument though.

Where the heck is that hero flag... because this was getting on my nerves.

fixed on trunk and branch (I hope!)