Closed Bug 783040 Opened 13 years ago Closed 11 months ago

Clicking on message in popup notification does not take you to message if Quick Filter is applied

Categories

(Thunderbird :: OS Integration, defect)

Desktop
All
defect

Tracking

(Not tracked)

RESOLVED FIXED
138 Branch

People

(Reporter: firstpeterfourten, Unassigned)

References

Details

(Whiteboard: [fixed by bug 1955924])

Preconditions: Open a mail folder (e. g. INBOX) and filter the messages on some term. 1. New mail arrives in the INBOX. 2. Popup notification is triggered, showing subject line and other information. 3. User finds a message interesting and clicks on it. Expected behavior: 4. User is brought to the place in the main Thunderbird interface where s/he can read the message. Actual behavior: 4. User is brought to the folder containing the message (here, INBOX). The message does not match the quick filter, so it is not displayed in the list and it is not shown to the user. 5. User is confused. S/he just clicked on a link for a message about one topic and is presented with something completely different. This surprise and attempt to make sense of the result of clicking there may result in the user forgetting what the original message was, and even if the user can remember, the user can't find the original message. Attempts to check other folders and eventually return to the original folder (INBOX here) will be confusing but successful because it causes the Quick Filter to be dropped. Noticing that a Quick Filter has been applied and that that is the reason why the message isn't displayed is not all that intuitive or obvious to the average user; even those aware of this workaround (simply removing the quick filter) must then scroll to find the target message in the list.
I have noticed this behaviour too and was going to submit a similar bug. One thing I've noticed is that this unwanted behaviour only happens if Thunderbird is currently showing a quick filter in the Inbox (assuming the new message comes to the Inbox). If Thunderbird is currently showing a quick filter in a different folder and the message notification is clicked, Thunderbird will change to the Inbox and display the message correctly - i.e. will do the expected behaviour. This makes the bug even worse, as the expected behaviour will happen some times and not others, depending on what folder was last displayed compared to what folder the new message appears in. I agree with WBT that, when clicking on an email notification, the message should be displayed (i.e. the quick filter should be cleared if necessary). There is an interesting debate to be had as to what the behaviour should be if the new message would be included in the quick filter results, e.g. if the quick filter was set to show just Unread, or another criteria that the new message matches - should the quick filter be cleared or not when clicking on the notification in that situation?
Severity: normal → S3

Does this still reporoduce in version 115, due on a few weeks?

Flags: needinfo?(john.mozilla)

(In reply to Wayne Mery (:wsmwk) from comment #2)

Does this still reporoduce in version 115, due on a few weeks?

Sorry, I'm not able to test the beta version.

Flags: needinfo?(john.mozilla)

I am referring to RELEASE version 115 due in a few weeks.

Flags: needinfo?(firstpeterfourten)
Flags: needinfo?(john.mozilla)

Because of longstanding unfixed bugs in core functionality, I no longer use Thunderbird. However, my initial bug report above is detailed and specific with testable steps for reproduction so that any other contributor can verify if it is still an issue.

Flags: needinfo?(firstpeterfourten)

I finally got round to testing and this is still happening with 115 (specifically 115.2.3).

Flags: needinfo?(john.mozilla)

Thanks John.

See Also: → 1955924
Status: NEW → RESOLVED
Closed: 11 months ago
Depends on: 1955924
OS: Windows 7 → All
Hardware: x86 → Desktop
Resolution: --- → FIXED
See Also: 1955924
Whiteboard: [fixed by bug 1955924]
Target Milestone: --- → 138 Branch
You need to log in before you can comment on or make changes to this bug.