User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112605 Minefield/3.0b2pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20071031 Thunderbird/220.127.116.11 ID:2007103104 "Mark Folder Read" appears in the contextual menu for mail folders. It would be great if it could be there for saved searches (virtual folders) as well (along with the Ctrl-Shift-C shortcut.) Currently, I have to do a select all, and then hit "m" to toggle the read/unread status. Reproducible: Always Steps to Reproduce: 1. Right-click a saved search. Actual Results: There is no "Mark Folder Read" option. Expected Results: There should be a "Mark Folder Read" option.
This is still not implemented in Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090121 Shredder/3.0b2pre. Confirm!
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
I think this bug is important again, with the new smart inbox feature introduced in the latest beta's (since smart inboxes are just a special way of saved searches, i think) Smart inboxes need to have the same features as normal inboxes have! This would confuse new users imho.
There are two ways to do this: 1. Make mark all read on a saved search iterate over each of the folders in the scope, pull out the cached search hits for that search in the scope folders, and mark the unread messages read via the folder. This potentially will operate on slightly stale data since I don't think we update cached hits when closed saved searches have new messages added. 2. Open a hidden cross-folder virtual folder view, update the saved search, and call mark all read on the hidden view. But first we'd need to make that work on cross-folder views, which I don't think it does currently...
cc-ing myself, doing some mxr-ing, maybe taking.
(In reply to comment #6) > cc-ing myself, doing some mxr-ing, maybe taking. If you have any question ask them here or on mozilla.dev.apps.thunderbird :-)
You need to log in before you can comment on or make changes to this bug.