User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:22.214.171.124) Gecko/20100914 Firefox/3.6.10 Build Identifier: Thunderbird/3.0.8 In version prior to 3.0.8 the prefs setting "mailnews.scroll_to_new_message "false"" prevented the display of the next message when deleting or moving a message or when switching folders. In 3.0.8 this setting has no effect and the next message will be displayed. Reproducible: Always Steps to Reproduce: 1. Select any message 2. Read and delete the message or move the message to another folder 3. Next message is displayed. Actual Results: Read any message in any folder. Delete it. The next message in the folder will be displayed. Expected Results: With scroll_to_new_message set to false the next message should not receive focus or display. A blank mesage window should show and focus should be off any message. This was working properly immediately prior to update to 3.0.8. Immediately after updating the behavior deviated. I searched all prefs files for the setting. It is there and set to "false". Also added the setting to the user.js file with no change. Thunderbird was restarted each time.
Do you see the same behavior in -safe-mode (http://support.mozillamessaging.com/en-US/kb/Safe+Mode)?
(In reply to comment #1) > Do you see the same behavior in -safe-mode > (http://support.mozillamessaging.com/en-US/kb/Safe+Mode)? Yes. Same behavior as noted in original report.
Tom could you spend a little bit of time to figure out when this started happening. There's a tutorial at http://www.rumblingedge.com/2009/02/24/howto-find-regression-windows-through-manual-binary-search/. Thanks in advance.
Been on this for quite awhile, had checked that I seem to be able to reproduce this in Miramar Alpha 3 and even as far back as: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20100101 Shredder/3.2a1pre
Assignee: nobody → gary
Assuming I tested correctly, this might even have occurred as far back as: version 1.6a1 (20060101) (not sure why it seemed to work for reporter, I couldn't get it to work at all) Did a bit of detective snooping at MXR, http://mxr.mozilla.org/comm-central/search?string=scroll_to_new_message&find=&findi=&filter=^[^\0]*%24&hitlimit=&tree=comm-central shows up: http://mxr.mozilla.org/comm-central/source/suite/mailnews/msgMail3PaneWindow.js#114 (seems to be SM) and: http://mxr.mozilla.org/comm-central/source/mail/base/content/folderDisplay.js#1080 This line was last changed in: http://hg.mozilla.org/comm-central/diff/b0e37b312b54/mail/base/content/folderDisplay.js or http://hg.mozilla.org/comm-central/rev/b0e37b312b54 which is asuth's folder display refactoring mega-bug. Nothing was changed at that line since then, but I'm not arrowing that change as the regressing bug here as it did not seem to even work for me prior to that changeset. asuth, what might be the issue? Wayne, anything related comes to mind?
Assignee: gary → nobody
Tom, can you reproduce this using a current version of thunderbird? if you are unable to reproduce, please close by setting status to resolved, and resolution to WORKSFORME or another appropriate setting. If you are able to reproduce, please add new details
Whiteboard: [closeme 2012-04-01][dupeme?]
This still exists in 10.0.2 release. (In reply to Wayne Mery (:wsmwk) from comment #6) > Tom, > can you reproduce this using a current version of thunderbird? > > if you are unable to reproduce, please close by setting status to resolved, > and resolution to WORKSFORME or another appropriate setting. > > If you are able to reproduce, please add new details
rsx11m has commented on this in the past. perhaps he will do so here as well :) ref: http://forums.mozillazine.org/viewtopic.php?f=39&t=573872&st=0&sk=t&sd=a&start=0 http://groups.google.com/group/mozilla.support.thunderbird/browse_thread/thread/2d84730d16c2c582?pli=1 https://github.com/protz/GMail-Conversation-View/issues/491 sadly, there is no description at http://kb.mozillazine.org/Mail_and_news_settings
Whiteboard: [closeme 2012-04-01][dupeme?] → [dupeme?]
Sorry, no idea. I only know about this preference within the scope of opening a folder at the first new message, which seems to work fine with IMAP accounts (but as you can see from the MZ thread you've referenced above it's not conclusive).
You need to log in before you can comment on or make changes to this bug.