166342 - next unread news does nothing if all messages are read and a new one arrives

Status: RESOLVED FIXED

(MailNews Core :: Backend, defect)

Description

[hana.skoumalova]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1b) Gecko/20020902
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1b) Gecko/20020902

If I read all messages in a newsgroup and leave focus on that newsgroup I can't
read new messages which arrive later by pressing 'N'. I have to move focus to
anothe group or to a mail folder. After pressing 'N' I get the dialog box about
moving to the newsgroup with a new message.

Reproducible: Always

Steps to Reproduce:
1. Read all new messages.
2. Leave focus on the newsgroup.
3. Wait for some new messages in that newsgroup (the newsgroup name gets bold
and a number of new messages is displayed).
4. Hit 'N'

Actual Results:  
Nothing.

Expected Results:  
Move focus to the next unread message and display it.

There is an easy workaround - I move focus on another newsgroup and then 'N'
works as expected, but it is several more hand-moves.

I am using the modern theme. 

This bug is quite old, but there were more annoying ones and that's why I'm
reporting it only now.

Comment 1

[Stefan Fleiter (:sfleiter)]

Same over here using Mozilla release 1.1 for Linux.

Comment 2

[Jouni Aro]

Me too, would like to get this solved.

NT & Mozilla 1.2a

Comment 3

[Daniel Wang]

*** Bug 177473 has been marked as a duplicate of this bug. ***

Comment 4

[Stefan Fleiter (:sfleiter)]

Please can the owner of this bug or anybody else who is allowed to set Hardware
and OS to all (see commect #2 and comment #3)?
Maybe this helps to get some attention on this.

Comment 5

[Konstantin Stefanov]

It is still here in Thunderbird 2.0.

Comment 6

[Wayne Mery (:wsmwk)]

next fails for both SM and TB. I did not check for dupes.

I set check for messages every 1 minutes. Post new message, after x minutes  unread count goes up when message detected, but thread pane doesn't get the new message(s).

Comment 7

[Stefan Fleiter (:sfleiter)]

This still happens with Thunderbird 3.0 Beta 4.

Comment 8

[Joshua Cranmer [:jcranmer]]

This should be fixed by bug 311774 under rc1 (I didn't get the fix in time for b4...).

Comment 9

[Stefan Fleiter (:sfleiter)]

Thanks, will test this when rc1 is released.

Comment 10

[Stefan Fleiter (:sfleiter)]

This works with Thunderbird 3.1.4.

Comment 11

[Konstantin Stefanov]

Yes, this was really fixed somewhere around 3.1 (and definitely works in 3.1.4)

I think status should be set to RESOLVED FIXED.

Comment 12

[Joshua Cranmer [:jcranmer]]

Per comments 8, 10, and 11, this was fixed by bug 311774.