272747 - message incorrectly marked as read when preview imap message

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[Dave Beavan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I have "Mark message read after displaying for" unchecked in the advanced
options.  As soon as I select a message from my Novell imap server it is
immediately marked as read. If I check the option and set a time it does wait
that length of time, but I prefer to have it never mark as read when previewing.

Reproducible: Always
Steps to Reproduce:
1. Under options, advanced, mark message read after display set to unclecked,
leave default of 5 seconds in box
2. Single click on imap message, preview appears correctly

Actual Results:  
Notice previewed message is marked as read

Expected Results:  
I would expect the message to stay marked as unread

Comment 1

[Dave Beavan]

Perhaps this is not a programming bug after all.

I read the "Mark message read after displaying for" checkbox to mean:
* yes - the message would be marked as read, with the delay being specified
* no - the message is never marked as read

But it can be read another way, which I suspect is the design:
* yes - the message would be marked as read with the following delay
* no  - mark the message as read immediately

If this is the case, and I misinterpreted the options could someone reassign
this issue as a minor bug against the options dialogue?

D

Comment 2

[John Lemon]

Duplicate of 234121, 262252, and others.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.