Closed Bug 378075 Opened 18 years ago Closed 16 years ago

typing n to go to next newsgroup, displayed message's header not visible

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ray, Unassigned)

Details

version 2.0.0.0pre (20070412) I now only read mail and news by typing "n" from each message. As I do this, I will see this at least once. It does not happen every time, but it does happen somewhat frequently. It is not rare. I will type "n". I will see a confirmation dialog checking that I want to switch to the next newsgroup. I hit the "Yes" button. The first unread message in the other newsgroup becomes visible in the message body pane, but as I look at the headers in the headers list above it, the header of the current message is not visible. Usually, the message header list is showing the bottom of the list, and the first unread message is above that. I can page up in the message header list and find the currently selected message header. But why should I have to? The currently selected message should be visible in the message header list.
Confirmed and agreed: the message header list should be scrolled so that the current message is shown in the list. Thunderbird 2.0.0.12 (20080213) on MacOS X 10.5.2 (Intel).
I just found this setting in another bug, which could be helpful in this case: user_pref("mailnews.scroll_to_new_message", false) Edit this value in the advanced configuration (about:config).
Well, this makes a fix to this bug easy, yes? Just change the default value of that preference.
Assignee: mscott → nobody
This is WFM in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090123 Shredder/3.0b2pre with pref set to both true or false - the default apparently is false. please reopen if you still see this in current trunk
Status: NEW → RESOLVED
Closed: 16 years ago
Component: General → Mail Window Front End
QA Contact: general → front-end
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.