Closed Bug 509401 Opened 15 years ago Closed 15 years ago

Messages always marked as read when viewed, even if for less than settings require.

Categories

(Thunderbird :: Mail Window Front End, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 506109

People

(Reporter: mozilla_bugs_peep, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090806 Gentoo Firefox/3.5.2 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090727 Thunderbird/3.0b3 I have messages set to be marked as read after 5 seconds of viewing. Thunderbird 3.0 beta 3 (and likely previous betas for 3.0) always marks messages as read after 5 seconds, even when they are not viewed for the full 5 seconds. Reproducible: Always Steps to Reproduce: 1. Click an unread message to view it. 2. Click another message (in under 5 seconds) 3. Wait for the 5 seconds to elapse 4. Notice that the original message has been marked as read. Expected Results: The message should not be marked as read unless it is displayed for 5 seconds. This happens for my POP accounts as well as my IMAP accounts.
This Works for me on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3pre) Gecko/20090809 Shredder/3.0b4pre.
Component: General → Mail Window Front End
QA Contact: general → front-end
Version: unspecified → Trunk
I see the problem on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 as well. Note about reproducing: the other message (not the "original" one that gets marked as read incorrectly) must be already marked as read itself. If you have two unread messages, only last one (the one you wait on) will be marked as read. (Which is the correct behavior.) Further, if you have 3 unread messages, and click on each of them in turn and wait on the third, it will act correctly. Only the last one will be marked as read. If you have 2 unread and one read message, clicking on each of the unread messages and then wait on the already read one. The last *unread* message you clicked off of will be (incorrectly) marked as read. Just to make sure, with this additional information, does it still work for you on 3.0b4pre?
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Keywords: regression
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.