Open
Bug 303462
Opened 19 years ago
Updated 2 years ago
Search folders should display number of messages in brackets
Categories
(Thunderbird :: Mail Window Front End, enhancement)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: orangenormal, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Currently, a search folder will display the number of unread messages in brackets beside the folder title. For most searches, I'd rather have it display the number of messages inside the search folder. This is useful, for example, when you create a folder of all 'flagged' messages. Reproducible: Always
Comment 1•19 years ago
|
||
Does the status bar telling the number of messages not suffice? This would create confusion and be inconsistent UI IMO.
Component: General → Mail Window Front End
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
The status bar only tells you the number of messages in the search folder if you click on that folder. This means if you'd like to see if there are any messages you have not followed up on, you'd have to manually click on (and check) the folder anyway. Microsoft Outlook 2003 displays the number of messages that still have follow-up flags beside the search folder on that criteria; this makes sense, since you've generally already read messages that you need to follow up on (so the read status isn't particularly useful). As for UI consistency, why not display what the number represents as well? This is arguably more clear than the current "number only" display, too. i.e.: Inbox (2 unread) Follow-up (15 flagged) ...
Updated•18 years ago
|
QA Contact: front-end
Updated•16 years ago
|
Assignee: mscott → nobody
Comment 3•14 years ago
|
||
Extra Folder Columns https://addons.mozilla.org/en-US/thunderbird/addon/9716/ does this.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•