552850 - Context menu "Mark newsgroup read" followed by quick focus on another newsgroup can mark the incorrect newsgroup as read

Status: RESOLVED INCOMPLETE

(Thunderbird :: Folder and Message Lists, defect)

Description

[Ed]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3

Under certain conditions, I sometimes see Thunderbird mark the incorrect newsgroup as read.  I suspect there may be a race condition between the mouse focus and the determination of the newsgroup associated with the context menu.

It seems to happen more often when I'm first reading news in the morning - basically, when the news retrieval is pretty busy.  I think that may give me just enough time to get a focus click in the way before the context menu determines its newsgroup.

Reproducible: Always

Steps to Reproduce:
1. Have a lot of newsgroups to load, with a reasonable number of posts to retrieve.  In other words, set things up so that Thunderbird has a lot to manage when retrieving new posts across all groups.

2. Collapse / expand the news account in the folder list to trigger the news update.

3. While the news update is in process, right click on a group and choose to mark the newsgroup as read.

4. Very quickly, left click on another group.
Actual Results:  
Most of the time, the behavior is correct:  the group associated with the context menu is marked as read.  Every now and again, the incorrect group (the one chosen with the left click in step 4) is marked as read.

Expected Results:  
Every time, the group associated with the context menu should be marked as read.

Marking as minor since there's an easy workaround (wait until all the newsgroup loads are complete, or move your mouse a little slower).

Comment 1

[Ludovic Hirlimann [:Usul]]

Do you also experience it in safemode ? (see https://support.mozillamessaging.com/en-US/kb/Safe+Mode for more information)

Comment 2

[Ed]

Yes, I was able to repeat the bug in safe mode.

Comment 3

[Wayne Mery (:wsmwk)]

Reporter, 

do you still see this problem when using a current version of thunderbird? 

And if you do not, please close bug report by changing resolution to worksforme

Comment 4

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.