Closed Bug 506618 Opened 15 years ago Closed 7 years ago

New messages automatically selected when new mail is received, and thus marked unread

Categories

(Thunderbird :: Folder and Message Lists, defect)

defect
Not set
critical

Tracking

(blocking-thunderbird3.1 -)

RESOLVED WORKSFORME
Tracking Status
blocking-thunderbird3.1 --- -

People

(Reporter: standard8, Unassigned)

Details

(Keywords: dataloss, qawanted)

STR:

1) Select Inbox folder of IMAP account.
2) Select an email, and then deselect it.
3) Wait for new mail to come in (doesn't have to come into the folder, can be filtered to other folders).

Actual Results:
Selects the email.

Expected Results:
No mail selected.

I'm also marking this dataloss as I'm 90% sure I've seen instances where somehow TB has selected a new, unread email and due to the policies I use that gets marked as read - hence I've lost the fact it is new (and it is also plain annoying that TB is changing the UI without me telling it to).
Flags: blocking-thunderbird3+
The Thunderbird drivers wish to release Thunderbird 3 as soon as possible. As a
result, we feel that this bug shouldn't stand in the way of all the other good
work getting into the hands of users sooner rather than later. Therefore we are
retargeting it for 3.1. See http://ccgi.standard8.plus.com/blog/archives/242
for more details. The 3.1 release is expected to be a quick release soon after
Thunderbird 3.
Flags: blocking-thunderbird3.1+
Flags: blocking-thunderbird3-
Flags: blocking-thunderbird3+
Target Milestone: Thunderbird 3.0b4 → ---
(In reply to comment #0)
> I'm also marking this dataloss as I'm 90% sure I've seen instances where
> somehow TB has selected a new, unread email and due to the policies I use that
> gets marked as read

I can confirm Mark's steps, though I have mark read after Nsecs disabled. Is there such a thing as minor dataloss? :)

similar to bug 284030 Clearing quicksearch marks unread mail read.

it's like the view is cleared, then reinstates the previous view, forcing "remembered & select last selected message".  ISTR hearing this also in context of using compact.
Severity: normal → critical
I don't think this would block 3.1, so minusing for now.  However, if this bug is a regression from Tb2, that might change.  Setting qawanted in the hopes that someone from QA will help figure that out.
blocking-thunderbird3.1: --- → -
Flags: blocking-thunderbird3.1+ → wanted-thunderbird+
Keywords: qawanted
does this still reproduce?
Flags: needinfo?
(In reply to Mark Banner (:standard8) from comment #0)
> STR:
> 
> 1) Select Inbox folder of IMAP account.
> 2) Select an email, and then deselect it.
> 3) Wait for new mail to come in (doesn't have to come into the folder, can
> be filtered to other folders).
> 
> Actual Results:
> Selects the email.
> 
> Expected Results:
> No mail selected.
> 
> I'm also marking this dataloss as I'm 90% sure I've seen instances where
> somehow TB has selected a new, unread email and due to the policies I use
> that gets marked as read - hence I've lost the fact it is new (and it is
> also plain annoying that TB is changing the UI without me telling it to).

Mark was this with "Automatically mark as read" unchecked?

I can't currently reproduce.
Flags: needinfo? → needinfo?(standard8)
No idea - too long ago. I doubt it though, I don't normally have that unchecked.
Flags: needinfo?(standard8)
(unlikely this would be Mac-only)

I wasn't able to reproduce.

Is this type of issue reported in support forums, or can you reproduce?
Flags: needinfo?(unicorn.consulting)
Flags: needinfo?(tanstaafl)
OS: Mac OS X → All
Summary: Messages automatically selected when new mail is received. → New messages automatically selected when new mail is received, and thus marked unread
James are you able to reproduce this?
Flags: needinfo?(unicorn.consulting)
Flags: needinfo?(jamesrome)
Flags: needinfo?(emoore)
I do not see this on my Mac
Flags: needinfo?(jamesrome)
thanks James
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.